• Community
  • Products
  • Jira
  • Questions
  • How come the Velocity and Sprint reports story points don't match what is shown in an active sprint's story points?

How come the Velocity and Sprint reports story points don't match what is shown in an active sprint's story points?

The current behavior of JIRA is that you can update story points to a story in an active sprint, but if you do that, the Sprint Report shows the # of when the sprint started.  The "Velocity Report" is also behaving the same way.  It shows the bar graph using the ORIGINAL story points at the start of the sprint.  This is also of no value.  When we finish the sprint we need to know WHAT we got done and it needs to reflect reality so the reports we share with management are accurate?  Any plans to fix these 2 reports?

1 answer

Hi Robert,

I think Atlassian did plan it that exactly way. Both this reports will show you the amount of value you had in your Sprint by the time you started it, they will never show you the values you changed afterwards.

If you want a report that can show you all this information, maybe you can try the Burndown Chart, as it will always have all your Sprint information, the committed value at the start and every change made on it.


I hope it helps!




That's of little value to the entire software dev process. Story Points change, that's a fact because as we learn more about it our refine in a sprint. We don't live in the perfect work where we know everything before a sprint starts. Also, the burndown chart is very cluttered and is not something I want to share with Management. It would be nice to have an option on the SPRINT and VELOCITY reports to show actual values. Probably a very easy change too:)

This is currently deliberate because the report is trying to show the effort that the team originally committed to (and therefore the estimate that will form their velocity). For velocity to be meaningful all stories need to be estimated with the same level of non precision, i.e. if you have 50 stories in the backlog and estimate them all with no pre-knowledge then from Sprint to Sprint you can measure how many points of equally unknown work can be completed. If you add additional knowledge to some stories but not others (by changing their estimate) you can no longer compare your velocity against these 'more known' stories to items further down in the backlog where you don't have that knowledge. The Sprint report will also show you the value committed, but it will contain any other issues added after its start.

Andre, I understand your point, but this is hurting our team not because we re-sized stories but because we split off part of a story out of a sprint. We had an 8-point story which we split into one 3-point and one 5-point story, and moved the 5-point story out of the sprint. The Velocity chart, however, shows that we completed all 8 points in the sprint, which is not true!

We did exactly the same thing as David - possibly bad agile practice agreed, but sometimes things happen :-) I also tried changing sprint scope by moving the story to be split out, reestimating it (smaller), creating the new story for remaining work, moving it back in to active sprint, moving to done... didn't change the sprint report value even though. My clumsy workaround (which did work) was to move the original story out of the active sprint, moved it to a "Won't Fix" release (or you could just delete it), create a new story with the 5 point value, move to active sprint, move to done in active sprint. Hey presto, job done.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Jan 08, 2019 in Jira

How to Jira for designers

I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...

810 views 3 9
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you