Burndown chart: Non-current sprint data

[Melissa Clark]

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?

[Nic Brough -Adaptavist-]

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.