-
Bug
-
Resolution: Unresolved
-
Low (View bug fix roadmap)
-
None
-
7.1.2, 7.1.9
-
None
-
7.01
-
5
-
Severity 3 - Minor
-
0
-
Summary
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
Environment
- JIRA Software 7.1+
Steps to Reproduce
- Create an issue and place it at the bottom of the backlog
- Create new Sprint
- Add newly created issue to the sprint
- Start Sprint
- Stop Sprint and choose to return issue to backlog
Expected Results
Issue is placed at top of the backlog
Actual Results
Issue returns to the bottom of the backlog
Notes
Problem is not present in JIRA 6.4.x
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.
- is related to
-
JSWSERVER-13636 When a sprint is completed incomplete issues should return to the top of the backlog
- Closed
Issue is very annoying and harm the basic operation for sprint planning . Can`t understand how the priority of this bug is low .