Assigning an issue to multiple milestones #797
Comments
Per "Mastering Issues":
Milestones are designed for tracking iterations in your development cycles, whether it be versions or some other system. It does not make sense to assign two milestones to an Issue. Labels are a much better system for tracking this sort of information. Something to the effect of |
Thanks @bardiharborow .. you make a good point, and after some thought, I think that's how we'll handle it. 👍 |
We can have hyperlinks to views of issues that show, e.g., only |
What if the issue is a bug that appears in two separate versions that have different release cycles, e.g. major v1 gets monthly maintenance releases, but major v2 won’t ship for another quarter? Do you create a different, duplicate issues that have v1 milestone and a v2 milestones respectively? How do you sync those issues? |
@jmakeig you make a valid point. I suppose my opinion stemmed from the fact I work mainly in continuously deployed environments where you don't have a old version to backport fixes to. |
This issue duplicates #441 |
+1 In my case, our process does not match Github's anticipated usage. We have multiple teams with multiple milestones where issues occasionally overlap and the teams goals converge. When separate teams converge on issues that is an indication (and opportunity!) that greater cooperation and coordination is required. |
Our organization would like to be able to assign an issue to multiple milestones.
In our case, this is because management wants to track some things that they require to sign off on this stage of our project, we developers also want to track some things that we require to sign off, and some are overlapping.
It seems initially that this feature is implemented...
@mattbrunetti mattbrunetti modified the milestone: Developer Acceptance, Management Acceptance a minute ago
But! When I click "Milestone" in the right-hand panel again, only "Developer Acceptance" is checked, and when I view the Management Acceptance milestone, the issue is missing.
Please fix, pretty please?
Thanks :)
The text was updated successfully, but these errors were encountered: