Why is an issue that was removed from a sprint not showing in the sprint report?

[Michael Byrne]

I removed 2 issues from my current sprint today. 1 issue shows on both the sprint report and the sprint burndown report. The other does not. Why?

[Michael Byrne]

I found that it is a known bug:

https://jira.atlassian.com/browse/JSWSERVER-14984

with no fix date....

[Michael Byrne]

I have more information.

Issue 1 was in sprint A, wasn't completed, so rolled into Sprint B when Sprint A ended. Issue 2 was in Sprint B. Then both Issue 1 and Issue 2 were removed from Sprint B. 

On the  burndown chart, it shows Issue 2 as being removed, but Issue 1 does not show up on either report. It's as if Issue 1 was never in Sprint B. 

Removing issues from sprints due to reprioritization happens often and I need to keep track of what was removed.

To answer the above question: Yes, the issues match the board's filter.

[Petter Gonçalves]

Hello @Michael Byrne

Thank you for reaching out.

It will be hard to precise describe why one issue appears in your Sprint Report while the other one doesn't, however, the Sprint report documentation provide us the scenarios required for an issue to appear in the report:

- The Sprint Report is board-specific – that is, it will only include issues that match your board's saved filter.

- The Sprint Report includes only issues that were completed while the sprint was in progress

Can you please confirm if both issues match the scenario above, even now when they are not added in the current Sprint?

Additionally:

- Verify on both issue histories what other issue movements and Sprint changes were performed.

- Check if the status of the issue that is not appearing in the Sprint report is properly mapped to your board columns.

Let us know if you have any questions.