Past Sprint Data Keeps Changing

[Julia Casciato]

Hi ! We are using Sprints in Jira Cloud, but I've noticed that data for completed sprints keeps changing after they are done, so I've been manually documenting the reports to figure out what is happening.

I had Sprint A from Dec 26 to Jan 9, and Sprint B from Jan 9 to Jan 22.

When Sprint A was first done, the completed story points was 41 and contained a list of 18 Jira tickets.

After Sprint B completed, I went back to Sprint A and saw the list changed to 22 story points and a list of 13 Jira tickets. So at some point in that 2 week period, 5 Jira tickets are no longer being counted toward Sprint A data. 

I confirmed in the 5 Jira tickets that the original sprint data is still on the tickets.

Does anyone know why tickets are "removed" from data on completed sprints? The only thing I can think of is that it's status related.

Currently, an item is considered Complete when it moves into "Code Review" (the last column of the sprint board, which also contains other statuses). The ticket won't have a resolution for a few more transitions, so it's possible an item can be "complete" in one sprint but not have a resolution for a few sprints later. Could this be impacting the data?

[Walter Buggenhout · Accepted solution]

Hi @Julia Casciato,

An item is considered complete when it reaches the rightmost column of the board. Just looking at the name of your last status on the board (code review), it seems very likely that your issues move to other statuses later on as your workflow probably contains additional statuses.

As issues move on afterwards, they quite literally fall off the board. I am wondering it is just that or if you additionally also exclude issues in certain statuses through your board filter. While I don't have a similar test environment available to verify, I would first of all look at that boar filter. If it excludes issues in certain statuses, I can imagine that they also disappear from your board and associated reports altogether. If your filter doesn't exclude issues in statuses that follow code review, I would suggest to check what happens when a single issue moves from code review into a next status to see how this impacts your report.

Hope this helps!

[Julia Casciato]

The filter was excluding tickets with a resolution. I removed that and all the data seems more accurate.

Thanks!