Sprint Report shows issues that were removed from the sprint in the "Issues Not Completed" section

[Kristi Rodgers]

After migrating over to a new Jira instance, I'm noticing an issue with our Sprint Report. It seems to be the same behavior that was described in this resolved bug:  https://jira.atlassian.com/browse/JSWCLOUD-8029

If an issue was in the sprint at one point in the past, even if the issue was removed from the sprint before the sprint began, I'm seeing it show up on the Issues Not Completed section of the Sprint Report. Any ideas?

[Alexey Pavlenko _App Developer_]

Hi @Kristi Rodgers ,

I haven't seen this issue. Probably, it's worth double-checking that the issue is not related to the migration. I would suggest creating a brand new board, adding issues, and repeating the actions.

By the way, if removed issues fall into the Not completed section, it may not be as bad as you think, since there are often cases where engineers remove issues from a sprint at the end of the sprint manually instead of waiting for the sprint completion.

Best regards,
Alexey

[Kristi Rodgers]

I don't understand your last comment; it's making our metrics look completely inaccurate. Things are being reflected as being a part of the active sprint when they're not, so it's very confusing. It affects our burndown visual as well. I will double check the migration cause by creating a new board and testing it out.

[Kristi Rodgers]

I just tested this out with a new project (rather than messing with our existing project). It functions as it should and only reflects items in the current sprint that are actually there. So if this is related to our migration, how do we fix it? It's like some issues lost a portion of their history and they're "stuck" as being reflected in sprints that they aren't in, even though the current Sprint field clearly shows that they're not in that sprint.

[Alexey Pavlenko _App Developer_]

@Kristi Rodgers ,

Last comment - engineers/product owners/scrum masters can remove issues that are a part of the indended sprint scope but cannot be completed by the sprint's end date. Therefore, they move these issues to some upcoming sprints or even to the backlog. When this happens, you also won't get accurate statistics on incomplete scope, since in this case such removed issues should also fall into incomplete scope.

Best regards,
Alexey

[Kristi Rodgers]

Those issues would fall under the "Issues Removed from Sprint" section of the Sprint Report rather than the "Issues Not Completed" section.

[Alexey Pavlenko _App Developer_]

@Kristi Rodgers ,

1. Check the 'History' tab of the issues, what does it show there? Are the issues still in sprints? How huge is the problem in your case - do you need to analyze closed sprints? If not, and you need to fix only active sprints, how many active sprints do you have? Probably, it's worth to submit a bug and starting fresh sprints and moving the issues there to save your time instead of spending time on the investigation or finding another workaround - probably, one of them could be to redo the migration in some other way.
2. They fall under "Issues Removed from Sprint", but it has a different representation on the graph.
   

Best regards,
Alexey