inconsistency between velocity chart and sprint report

Question

Hello,

For some time now it has been happening in one of our teams that there is an inconsistency in the number of story points committed when I look at the velocity graph versus the number of story points that appear when I consult the sprint details. I'll post a couple of images to give you an idea, one is from the velocity chart and the other is from the burndown chart of a specific sprint. For both images I have highlighted the committed story points and it can be seen that for the same sprint in the velocity chart approximately 240 story points appear while in the burndown report approximately 90 story points appear. Would you know what could be causing this difference between both reports?

Thanks in advance!

Valeriia_Havrylenko_SaaSJet · Answer

Hi @AgileHappyLearner @Kieran Williams 👋

We've noticed that at times, two Jira reports show different data. One scenario we've observed is when you remove an issue from a sprint and then mark it as resolved. One report counts it as resolved in the sprint, while the other does not. Please check if this is the case.

Also, if you switched to Cloud and open to the add-ons, you might want to try Time in Status, with Sprint Report. It provides a comprehensive look at sprint activities and data. This tool helps you monitor the progress and performance of completed sprints, enabling well-informed decisions.

You can also book a live session to ask any questions about the add-on. Add-on developed by my team.

I hope you find this helpful 🚀

Kieran Williams · Answer

Having the same issue - in my case I it looks like the velocity chart includes statistics for subtasks, whereas the burndown and others only do so for User Story ticket types.

(...adding this line so that I can post... the forum thinks I'm spamming because I answered same in two threads).

Bill Sheboy · Answer

I recommend using the JQL results to identify the issues which should have been marked as done for an earlier sprint, or not in the sprint, or...and then correcting that situation.  Otherwise the symptom will continue, as you see in your recently created sprints.