When I change story points during a sprint, it is not reflected in any reports. Why not?


1 answer

Because story points is a estimation statistic and it is supposed to be used for estimation i.e before the start of sprint. If you change story points in middle of sprint then it is classified as error in estimation. 

All the reports will only consider the story points you specified at the start of sprint. Velocity chart will only burn down that original story point value. Any change to it during sprint will not be recognised.

If you recognise that a story was underestimated then instead of updating the story points i recommend you update the remaining estimate and that way at least your burndown will be representative of the new change.


Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,156 views 13 19
Join discussion

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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot