Jira Burndown chart is missing the guideline or estimation data

Summary

When viewing the Jira Software Burndown chart report, the guideline is missing or the remaining estimation is not reflected.

Solution

Start time of the Sprint is incorrect or inaccurate

If you set the start time of the Sprint to a value in the past, the guideline will load incorrectly. 

When checking the current start date, consider the Jira timezone. If the Jira instance is set to a different timezone than the timezone your team uses, you may wish to check the timezone in your user profile and ensure that it is set correctly.

Solution

Edit the Sprint Start date using the Edit Sprint option on the backlog page. Set the Sprint Date to a more accurate time.

If issues are not estimated correctly in the chart

If any of the cases below apply to your sprint data, the only solution is to close the current sprint, re-create a new sprint, and make sure to associate the issues before starting the sprint.

Ensure estimation values are added before the start of the sprint and that the issues don't have release dates earlier than the start of the sprint. 

• Sprint was started before assigning any tasks to the sprint

• Sprint was started with issues that had no estimation values configured

  • For example, the story point or estimation of the issue was zero at the time of sprint start, and the estimation value was added later

• Issues were added after the sprint was started

  • Issues appear in the report as "Issue added to sprint" and estimation data will not display correctly in the chart

• Issues had a release date earlier than the start of the sprintand the guideline won't load correctly

• Issues were removed during the sprint cycle

• Issues were closed after the sprint complete date

• Issues were closed before the sprint complete date, but the issue status is not mapped to the rightmost column of the board

  • The single right-most column will always be green, representing items in a 'successful' state

Additional caveats about issue estimation

The chart does not use data from subtasks, even if your project's subtasks have their own estimates.

The report will only use data from standard-level issue types like Stories, Bugs, or Tasks.

• Known issues:

  • Negative remaining value on Burndown chart

  • JSWSERVER-20815 - Issue removed from Sprint not showing in Burndown Chart or Sprint Report when moving from Sprint to Sprint (fixed in 8.13.5, 8.19.1 and later)