Allow bulk carry-forward of remaining open merge requests & issues to another milestone when closing a milestone
Problem to solve
We really need a way to reschedule all issues across the board when a release/milestone has ended.
Allowing the organization to move all issues across the group in lock-step when a development period has ended would help with accurate work planning.
Target audience
Engineering managers and project management at GitLab.
Further details
We are now already in the end of 11.6
but in 11.4
and 11.5
we have:
- 18 open issues in 11.4
- 32 open MRs in 11.4
- 51 open issues in 11.5
- 117 open MRs in 11.5
header | header |
---|---|
If work is still being done in those issues and MRs it should be accruately captured per the milestone that it will be finished.
Proposal
Allow moving of all pending merge request & issues to another milestone when closing a milestone.
- MVC
- When closing a milestone add an option to close and also move remaning open MRs and Issues
- Allow only the selection of started or up coming milestones
- Nice to have
- Allow setting milestone to auto-close when past the due date
- Allow setting the next milestone the issues and MRs will be moved to when autoclosed
When we decide to close a past milestone, allow the option to move all remaining unfinished work to a milestone that has started or upcoming.
Jira has a mechanism for this when closing a sprint, the remaning issues can be moved to the next sprint or to the backlog.
What does success look like, and how can we measure that?
Accurate release work capture for GitLab engineering.