-
Suggestion
-
Resolution: Fixed
Currently issues will drop into a future sprint if one exists or to the backlog otherwise. This is inconsistent and causes confusion.
Update so that when closing a sprint with incomplete items the behaviour is predictable and enables better planning/organisation.
If no future sprints exist (in the board where the sprint is closed) move incomplete items to the backlog (placed according to rank)
If future sprints exist (in the board where the sprint is closed) give the options to move all items to:
- Named future sprint (pick one)
- Backlog (placed according to rank)
Consideration needed for incomplete work items in scenarios where not visible on the current board.
- duplicates
-
JSWCLOUD-6421 Option to decide where Unresolved Issues go to after a Sprint is completed or after being removed from Sprint
- Closed
- is duplicated by
-
JSWCLOUD-12333 Allow choosing where to put unfinished issues
- Closed
-
JSWCLOUD-11179 When running multiple sprints, I need to be able to specify which future sprint incomplete work is moved to
- Closed
-
JSWCLOUD-11192 When closing a sprint destination of incomplete issues can be selected
- Closed
- is related to
-
JSWCLOUD-10792 Message incorrect when ending a sprint with remaining issues
- Closed