-
Bug
-
Resolution: Answered
-
Low
-
11
-
Severity 3 - Minor
-
NOTE: This bug report is for JIRA Software Cloud. Using JIRA Software Server? See the corresponding bug report.
Steps to reproduce :
- Create an issue and add it to a future Sprint.
- Notice that it shows up on the backlog view of the Rapid board
- Now close that issue
- Notice that it disappears from the backlog view
- Now start the Sprint
- Notice that the issue suddenly appears in the Sprint as a closed issue
This is confusing for the users.
As stated by the Product manager
The expected behaviour should be as follows:
If an issue is closed and is not in an active sprint, it will not be shown in the Backlog (plan mode).
The issues (closed in a future sprint) should not appear in the sprint when it is started.
If is it required that an issue is to be closed in a future sprint then that sprint must be started with the issue included (prior to the issue being closed).
This is expected behaviour as the Backlog view is designed to serve as a "backlog" for Issues to be worked on. If an Issue is closed, by Agile methodology, the Issue should no longer be worked on and does not need to be part of the Backlog as this will conflict with the expected workload.
With that in mind, the actual bug here is that after being closed in a planned Sprint, once the Sprint has started, the closed Issue shouldn't re-appear in the Sprint view as the work is completed outside the Sprint and conflicts with the Velocity calculations.
- duplicates
-
JSWCLOUD-12185 Issues transitioned to Done status on planned sprint are not visible until sprint is started
- Closed
- is related to
-
JSWSERVER-11877 Issues closed in future sprints do not show up in the Backlog until the Sprint is started
- Gathering Impact