-
Suggestion
-
Resolution: Fixed
NOTE: This suggestion is for JIRA Software Cloud. Using JIRA Software Server? See the corresponding suggestion.
When a Sprint is completed, it would be useful to have the ability to decide where Unresolved issues should go, either:
- to the backlog
- to any other existing sprint
Same should apply to removing Issues from an ongoing Sprint.
- has a regression in
-
JSWCLOUD-13636 When a sprint is completed incomplete issues should return to the top of the backlog
- Closed
- is duplicated by
-
JSWCLOUD-6024 At the end of the sprint any incomplete issues are automatically moved into the top of the ‘next sprint’ instead of the backlog
- Closed
-
JSWCLOUD-7579 Ability to select destination for incomplete issues when closing a sprint
- Closed
-
JSWCLOUD-12597 Having the option to choose which sprint/backlog the unresolved issues should move to
- Closed
-
JSWCLOUD-13248 Ending a sprint - unclear message regarding what happens with in-progress tickets
- Closed
- is related to
-
JSWCLOUD-12777 Hidden unresolved issues to move to the next sprint after completion
- Closed
-
JSWCLOUD-13453 Destination Selection When Completing a Sprint Should Default to Next Scheduled Sprint
- Closed
-
JSWSERVER-6421 Option to decide where Unresolved Issues go to after a Sprint is completed or after being removed from Sprint
- Closed
-
JSWCLOUD-18440 When removing issue from an active sprint on board, prompt user where to place that issue, such as backlog or future sprint
- Gathering Interest
- relates to
-
JSWCLOUD-13154 Ability to set default action when completing a sprint.
- Closed