Why do completed story points differ on Release Burndown vs. Sprint Report

We just finished a sprint in which, according to the Release Burndown chart, the point stats look like this:

736 at start of sprint

42 added to version

6 completed

772 remaining


However, during the sprint we 'Resolved' a large story sized at 21 points because we're not going to do it (I can confirm this on my Sprint Report). So from a release standpoint, those 21 points need to come off of the 772 remaining points as well but as you can see, they haven't.

Why is this?


2 answers

Was that 21 point story moved to  the done column (or the rightmost column in your agile work mode), If not then it will not come off from the remaining estimate.


I changed the status without using the board and instead used the Resolve button. But I did confirm that Resolved status was (and is) in the last column of our board. Shouldn't that have the same affect?

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,293 views 14 20
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