Burndown chart shows old events when sprint start date is postponed

[Deepak VR]

Hello All,

Burndown chart is not updating when changing the start time of Sprint

I have started the sprint on 5th Dec for 2 weeks of duration which ends on 16th Dec.

Query is: I have started the sprint, after that team updated couple of hours, then to display the burndown accurate, i have adjusted the sprint start time to current tool time, but chart was not updated.

Same kind of update I use to do in old JIRA version, it was worked fine. but seeing this issue on latest version update. 

Please let me know if any has suggestions.

thanks

[Nic Brough -Adaptavist-]

Welcome to the Atlassian Community!

Do not adjust the sprint start time, it's misrepresenting what you are doing.  Leave it in place, and accept that your people adjusting in-sprint estimates are recording scope creep in the sprint.

[David Kuehlewind]

I just ran into this issue as well, but it wasn't from the team misrepresenting what they were doing. I did a bulk import with about 160 hours of half-hour tasks. Apparently the bulk import only accepts whole-number hours (even though it has to be entered in seconds), and so all of these tasks had 0 hour estimates. The new sprint was started overnight, and this morning the developers noticed that this particular set of tasks was all 0 hours. I did a bulk update to fix the durations, but now the burndown is off by ~160 hours. I adjusted the start time to get the chart to show with the correct burndown line, but the chart did not update.

Point is - it's not always the customer's fault for doing something wrong. There can be valid cases where the customer wants to change the start date. The tool used to reflect that in the chart. It no longer does. If "do not adjust the sprint start time" is the answer, why does Jira still have an interface to let you do it? If it lets you do it, it would be nice if the chart aligned as well, like it used to.