[Projects Beta] Have labels without converting to issue #15380
Unanswered
Mineinjava
asked this question in
Projects and Issues
Replies: 2 comments
-
|
I also would find this useful. I often have things I want to add to my project. But they need to be triaged/research/prepared some before I actually know what repo it is associated with. Having labels available would be great for adding categorization/organization. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Yeah, I don't want to have my project stuff public so I don't add as an issue but if I don't, I can't add labels. Despite the integration benefits of GitHub Projects, this is the one thing stopping me from using it as Trello already has labels. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
In the new Projects beta, projects can be tied to a user or organization instead of a repository. However, to label a task in the project board or list, it must first be converted to an issue inside a repository.
This can cause confusion when a project encompasses multiple repositories, and a task relates to multiple of these repositories.
Something like milestones within the projects could also be useful here, allowing users to set smaller goals. This would be especially useful to a "master project" where smaller projects and goals are delegated to groups or individuals. Milestones could also label tasks that contribute to the milestone.
Beta Was this translation helpful? Give feedback.
All reactions