-
Suggestion
-
Resolution: Duplicate
-
None
-
None
NOTE: This suggestion is for JIRA Software Server. Using JIRA Software Cloud? See the corresponding suggestion.
Problem Definition
As of JIRA Software 7.1, when completing a Sprint, a popup will appear allowing the Admin to choose a Destination for Incomplete Issues if there are Sprints Scheduled. By Default, the Backlog is Selected; in previous versions of JIRA Software (Agile), incomplete issues will be returned to the top of the backlog.
Current behavior: If you complete a sprint and then return all incomplete issues to the backlog then they will return to the location in the backlog they were before the sprint started. This means if you dragged them from the bottom (if you just created them for example) then they'll return to the bottom.
See related: Completing a sprint
Suggested Solution
Issues should always return to the top of the backlog, as they were just included in a sprint it should be assumed that they are a high priority and they should appear at the top of the backlog instead of their previous version.
Workaround
- Drag issues to the top of the backlog before adding them to your sprint.
- Create a future sprint and move incomplete issue there before closing the current sprint.
- duplicates
-
JSWSERVER-6911 As a user, I'd like current sprint issues to be ranked higher than backlog issues
- Gathering Interest
- is a regression of
-
JSWSERVER-6421 Option to decide where Unresolved Issues go to after a Sprint is completed or after being removed from Sprint
- Closed
- is related to
-
JSWSERVER-14618 Ability to select the position for remaining issues on sprint completion
- Gathering Interest
- relates to
-
JSWSERVER-15117 After closing a sprint incomplete issues doesn't return to the top of the backlog
-
- Closed
-
-
JSWCLOUD-13636 When a sprint is completed incomplete issues should return to the top of the backlog
- Closed
[JSWSERVER-13636] When a sprint is completed incomplete issues should return to the top of the backlog
Workflow | Original: JAC Suggestion Workflow [ 3066045 ] | New: JAC Suggestion Workflow 3 [ 3663309 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: Confluence Workflow - Public Facing v4 [ 2626273 ] | New: JAC Suggestion Workflow [ 3066045 ] |
Affects Version/s | New: 7.1.0 [ 59897 ] | |
Affects Version/s | Original: 7.1.0 Server [ 61099 ] |
Workflow | Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2323093 ] | New: Confluence Workflow - Public Facing v4 [ 2626273 ] |
Status | Original: Closed [ 6 ] | New: Resolved [ 5 ] |
Workflow | Original: JIRA PM Feature Request Workflow v2 [ 2041289 ] | New: JIRA PM Feature Request Workflow v2 - TEMP [ 2323093 ] |
Workflow | Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2031179 ] | New: JIRA PM Feature Request Workflow v2 [ 2041289 ] |
Workflow | Original: JIRA PM Feature Request Workflow v2 [ 1393749 ] | New: JIRA PM Feature Request Workflow v2 - TEMP [ 2031179 ] |
Description |
Original:
h3. Problem Definition
As of [JIRA Software 7.1|https://confluence.atlassian.com/display/JIRASOFTWARE/JIRA+Software+7.1.x+release+notes], when completing a Sprint, a popup will appear allowing the Admin to choose a Destination for Incomplete Issues if there are Sprints Scheduled. By Default, the Backlog is Selected; in previous versions of JIRA Software (Agile), incomplete issues will be returned to the top of the backlog. !J64_backlog.png|thumbnail! Current behavior: If you complete a sprint and then return all incomplete issues to the backlog then they will return to the location in the backlog they were before the sprint started. This means if you dragged them from the bottom (if you just created them for example) then they'll return to the bottom. !J71_backlog.png|thumbnail! See related: [Completing a sprint|https://confluence.atlassian.com/display/JIRASOFTWARESERVER071/Completing+a+sprint] h3. Suggested Solution Issues should always return to the top of the backlog, as they were just included in a sprint it should be assumed that they are a high priority and they should appear at the top of the backlog instead of their previous version. h3. Workaround * Drag issues to the top of the backlog before adding them to your sprint. * Create a future sprint and move incomplete issue there before closing the current sprint. |
New:
{panel:bgColor=#e7f4fa} *NOTE:* This suggestion is for *JIRA Software Server*. Using *JIRA Software Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JSWCLOUD-13636]. {panel} h3. Problem Definition As of [JIRA Software 7.1|https://confluence.atlassian.com/display/JIRASOFTWARE/JIRA+Software+7.1.x+release+notes], when completing a Sprint, a popup will appear allowing the Admin to choose a Destination for Incomplete Issues if there are Sprints Scheduled. By Default, the Backlog is Selected; in previous versions of JIRA Software (Agile), incomplete issues will be returned to the top of the backlog. !J64_backlog.png|thumbnail! Current behavior: If you complete a sprint and then return all incomplete issues to the backlog then they will return to the location in the backlog they were before the sprint started. This means if you dragged them from the bottom (if you just created them for example) then they'll return to the bottom. !J71_backlog.png|thumbnail! See related: [Completing a sprint|https://confluence.atlassian.com/display/JIRASOFTWARESERVER071/Completing+a+sprint] h3. Suggested Solution Issues should always return to the top of the backlog, as they were just included in a sprint it should be assumed that they are a high priority and they should appear at the top of the backlog instead of their previous version. h3. Workaround * Drag issues to the top of the backlog before adding them to your sprint. * Create a future sprint and move incomplete issue there before closing the current sprint. |
Link |
New:
This issue relates to |
Labels | Original: pse-request | New: affects-server pse-request |