Sprint Report: list of 'Issues Not Completed' includes issues that were removed from the Sprint before it was started

[Miles Tillinger]

Is this intentional? Product Owners for teams using JIRA Agile are creating an aspirational release plan a number of sprints ahead, but before the next sprint is started, some of the issues will be removed as they total more than the team's velocity.

Then when reviewing the Sprint Report mid-sprint, those issues that are no longer in the current sprint backlog are still in the report under 'Issues Not Completetd', which creates an unusable report.

[Dave]

Hi Miles,

It looks like you're running into this bug - https://jira.atlassian.com/browse/GHS-8029

Intentional behavior would be to include those if you had removed them after starting the sprint, but not during planning.

Cheers,

-dave

[Dave]

To add, unfortunately there isn't currently a workaround, but be sure to vote and comment on that issue to help raise the visibility to the project team (which means it will get fixed more quickly).

[Miles Tillinger]

Thanks David. Is voting for these issues the most effective method of getting them into a release? It's been open since March, and there's no fixVersion against it...

[Dave]

Unless it's a critical bug or blocker, voting is really the only way to impact getting them into a release. Non-critical issues are addressed based on a variety of considerations including how complex it is to fix, how many customers are affected, etc. One of the primary ways to measure impact is from the votes and customer feedback on the issue.