-
Bug
-
Resolution: Unresolved
-
Low (View bug fix roadmap)
-
None
-
7.12.0, 7.13.5
-
None
-
7.12
-
8
-
Severity 3 - Minor
-
0
-
Issue Summary
Once issues are moved to unmapped statuses on the board, and they are assigned to a New Sprint once the current sprint ends, the reports for New Sprint do not behave consistently.
Steps to Reproduce
- Add a status to the default workflow called "Cancelled"
- add a post function to set the resolution to "Won't do"
- on the scrum board make sure "Cancelled" is in the "unmapped statuses column
- Start a sprint (let's assume you have two issues in it ISSUE-1 and ISSUE-2)
- Mark ISSUE-1 as Cancelled (obviously by a method other than drag and drop
- See how it is no longer visible on the board
- Check the sprint report for this sprint, see how it lists ISSUE-1 as "removed from sprint"
- Now close the sprint. It will tell you that 2 issues were incomplete (I would expect to see 1)
- Choose to move the incomplete issues to a new sprint.
- See how there is only 1 issue showing in the backlog for the sprint.
- Look at ISSUE-1, see how it says it's in the new future sprint.
- Start the new sprint.
- See how the sprint report for the new sprint does not include ISSUE-1 in the list of issues added to the sprint.
- Check the Burndown Chart for the new sprint, ISSUE-1 is showing there.
Expected Results
Either the unmapped issue would be considered added/not added to the sprint by both reports.
Actual Results
- For the previous sprint:
- Burndown will show ISSUE-1 as issue completed
- Sprint report will show ISSUE-1 as removed from sprint
- For current/next sprint
Mapping the statuses to a column (if the status is "Cancelled", map the status to the "Done" column).
- mentioned in
-
Page Failed to load
The reports behave inconsistently whether or not you add the issues to a new sprint. When you move the issue to an unmapped status the Sprint Report says it has been removed from the sprint, however it actually has not. The Sprint Report will not report on issues that are not available on the board, however the Burndown Chart will.
There are a few things going on here. First of all, when the Sprint Report says the issue has been removed from the sprint it is clearly wrong. The issue does not have the sprint removed from it, however I would argue that removing the issue from the sprint as the Sprint Report currently reports it is the expected behaviour.
The second piece that doesn't feel expected is that when you close the sprint and choose to add incomplete issues to the new sprint that it would add issues that are not visible on the board to the new sprint. This behaviour means that issues are rolling through sprint after sprint with the user never seeing it.
Yes, the current behaviour is "working as designed" but the design is flawed. I'm assuming the same would happen if I changed the board scope to exclude the "Cancelled" status rather than just unmapping it. I'll test that when I get a chance.