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

1. Add a status to the default workflow called "Cancelled"
2. add a post function to set the resolution to "Won't do"
3. on the scrum board make sure "Cancelled" is in the "unmapped statuses column
4. Start a sprint (let's assume you have two issues in it ISSUE-1 and ISSUE-2)
5. Mark ISSUE-1 as Cancelled (obviously by a method other than drag and drop
6. See how it is no longer visible on the board
7. Check the sprint report for this sprint, see how it lists ISSUE-1 as "removed from sprint"
8. Now close the sprint. It will tell you that 2 issues were incomplete (I would expect to see 1)
9. Choose to move the incomplete issues to a new sprint.
10. See how there is only 1 issue showing in the backlog for the sprint.
11. Look at ISSUE-1, see how it says it's in the new future sprint.
12. Start the new sprint.
13. See how the sprint report for the new sprint does not include ISSUE-1 in the list of issues added to the sprint.
14. 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

1. For the previous sprint:
   • Burndown will show ISSUE-1 as issue completed
   • Sprint report will show ISSUE-1 as removed from sprint
2. For current/next sprint
   • The issue is considered to have been added to the sprint by the Burndown Chart.
     
   • The issue is considered to not have been added to the sprint by the Sprint Report.
     

     Workaround

Mapping the statuses to a column (if the status is "Cancelled", map the status to the "Done" column).