-
Bug
-
Resolution: Fixed
-
Medium
-
6.3.0.2
-
None
-
6.03
-
The symptom here is if you add an issue to a future sprint, then resolve it, then start the sprint, the issue appears in the sprint on Work Mode and Sprint Report/Burndown Chart.
There is a mild inconsistency with the reporting of the estimate value between Sprint Report and Burndown Chart. The Burndown Chart shows the issue coming into the sprint with a value of 0, regardless of the actual estimate. This is because the issue was already 'burnt down' before the sprint started. The Sprint Report on the other hand, shows the value of the estimate when the sprint started, which may be non-zero.
Therefore the fix here may be around making the reporting more consistent/accurate, or it may be around not bringing such issues into the sprint in the first place. The latter could be difficult to solve due to issues potentially appearing on multiple boards.
- causes
-
JSWSERVER-9983 Closing an issue in a planned (unstarted) sprint does not remove it from the sprint, causing errors when deleting the sprint
- Closed
- is duplicated by
-
JSWSERVER-10009 Already closed issues reappear in started sprint
- Closed
-
JSWSERVER-10492 Formerly Closed Issues show up once the planned sprint gets started
- Closed
-
JSWSERVER-11345 Improve How JIRA Agile Handle Closed Ticket in a Future Sprint
- Closed
- is related to
-
JSWSERVER-9797 Issue moved out of sprint before start, still shows on reports
- Closed
- relates to
-
JSWSERVER-11702 Close issue transition removes issues from planned (and not started) sprints
- Closed
-
JSWSERVER-12785 Resolving an Issue that is in the future sprint, removes it from the backlog but doesn't remove the issue from the sprint.
- Closed
-
SW-1571 Loading...