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 Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Julia Dillon
Posted Tuesday in Jira

Tell us how your team runs on Jira!

Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...

225 views 1 18
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