Burndown Chart Not Updating When Issue Created Date Is Changed

[Rebecca Vaught]

My team is utilizing sprint burndown charts. The sprint started on 1/17/2021 and ended 2/22/2021. We did not load the issues into Jira until 2/9/2021. When this is reflected on the burndown chart, it is represented as a scope change in the middle of the project and the grey guideline no longer trends down but is at 0. I understand this is by design because we technically started the sprint with 0 issues.

I exported my issues and updated the Created Date to be the start date of the sprint 1/17/2021. The issues successfully updated to reflect the new Created Date of 1/17/2021 but the burndown chart did not update at all.

Does anyone know a workaround for this? 

[Nic Brough -Adaptavist- · Accepted solution]

The burndown chart does not look at dates.  It looks at the issues that were/are in the sprint.

[Rebecca Vaught]

Thanks for the reply. That makes sense to me.