-
Bug
-
Resolution: Fixed
-
Medium (View bug fix roadmap)
-
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
-
-
- Closed
-
- is duplicated by
-
-
- Closed
-
-
-
- Closed
-
-
JSWSERVER-11345 Improve How JIRA Agile Handle Closed Ticket in a Future Sprint
- Closed
- is related to
-
-
- Closed
-
- relates to
-
-
- Closed
-
-
-
- Closed
-
-
SW-1571 Loading...
[JSWSERVER-9854] Issues which are added to a future sprint and resolved before the sprint is started still appear in the sprint
Florian Zink
added a comment - Any updates on this one? 
Dejan Stojadinović
added a comment - Any update for this issue ? One fix could be to use the method prior to 6.3:
A sprint is only attached to an issue when the sprint is started.
This worked fine before but with the new sprint feature this gets harder from the user perspective because closed issues disappear from plan mode (as expected).
From the application side it should however be a simple matter to detect if an issue is closed while in an "active sprint" or in a "future sprint".
- "active sprint" would behave like now
- "future sprint" would cause the sprint field to be cleared. It seems the information is already available as the issue states "future sprint" and "completed sprints" as two different things. So clearing the field should be okay and provide the expected behaviour.
Hello,
The Fix Version for this issue is 6.6.51.
We are using JIRA Agile 6.6.80 and it looks like this issue is still reproducible.
Steps to reproduce it:
1. Create an issue.
2. Add it to a sprint that is not started yet.
3. Resolve the issue.
4. Start the sprint.
Even if resolved/closed issues are not supposed to be displayed in "Backlog" mode ("Plan mode" in older versions), it will be present in the under the respective sprint. Removing it from the sprint will also affect the consistency of the reporting, as specified in the original description.
Best Regards,
Mihai