Milestones should live at the project level #8073
Unanswered
tleef
asked this question in
Projects and Issues
Replies: 4 comments 3 replies
-
+1 for this. We were about to raise exactly the same suggestion. We are working around this in the same way you are too, so are pleased to see it on the road map. |
Beta Was this translation helpful? Give feedback.
0 replies
-
+1 for this! Milestones should be on project and not repository level |
Beta Was this translation helpful? Give feedback.
0 replies
-
Duplicate of https://github.com/orgs/community/discussions/6296 (as this has more up-votes). See also current status. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Currently if I have a milestone that spans multiple repos, I need to duplicate the milestone in each repo.
Thankfully when grouping issues by milestone in a project table view, it groups the issues from all of the repos together so long as the milestones in each repo are named exactly the same.
Unfortunately this means that only issues can be placed in a milestone. If you have simple tasks or "items" that relate to the milestone but not to any repo, you are stuck tracking that task separately. This is exemplified by the "Cannot add items when grouped by milestone" message that you see on tables grouped by milestone.
My proposal is allow milestones to be managed at the project level. This way issues from any repo and even simple items can be added to a milestone and tracked.
Edit: Just saw that this is already on the roadmap 🙂
github/roadmap#276
Beta Was this translation helpful? Give feedback.
All reactions