Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Burndown chart: Non-current sprint data

It appears that the data/work down from the previous sprint dates on tickets that rolled over or were reopened in the consecutive sprint is accounted for in the current sprint. This is throwing of my data for the current sprint as to how much work was logged in the current sprint. Can this be changed, or am I reading this wrong, so that maybe it actually isnt counting previous sprint work logged towards the current sprint when reviewing the burn down chart?

1 answer

0 votes

Welcome to the Community!

This is the correct behaviour. 

Burndown measures delivery against commitment during the sprint.  It is not a partial measure, it is binary - an item is delivered during the sprint or it is not.

You can only burndown when the item is delivered.  Work actually done is irrelevant to the sprint estimate, all that matters is the delivery (or not) and hence burndown, as a measure of the current sprints delivery against commitment, doesn't look at it.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Software

👋 Looking for 15-20 volunteers to test Atlassian training content

Hi everyone! Are you interested in beta testing Atlassian University’s newest (unreleased!) training course? We’re looking for 15-20 volunteers to test our newest training course, Basic reporting...

761 views 24 28
Read article

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you