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?

Thanks

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.

Rahul

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 Sign up to answer
Community showcase
Posted Sep 18, 2018 in Jira

What modern development practices are at the heart of how your team delivers software?

Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...

20,770 views 2 7
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