Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Burndown Chart Not Updating When Issue Created Date Is Changed

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? 


1 answer

1 accepted

1 vote
Answer accepted
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Feb 25, 2021

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

Thanks for the reply. That makes sense to me. 

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events