Sprint burndown chart showing active sprint estimation to the future sprint end date
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
Sprint burndown chart showing incorrect data to the future sprint end date.
Environment
8.20.11
Diagnosis
The board sprint is estimated with the time spent
The board's active sprint is affected by the issue.
You have noticed that some issues are estimated more than 1 month in the future. Search for the issues worklog date in the future month using the JQL query:
1project = <project_key> and sprint = <sprint_name> and worklogDate >= startOfMonth(1)ℹ️ startOfMonth(1) = 1 month in the future.
⚠️ If none of the diagnosis steps matching here, please check the general burndown chart report troubleshooting guide - Missing Guideline in the Burndown Chart
Cause
The burndown chart report was showing incorrect data due to the worklog estimation was set to a future date.
Solution
Update the problematic issue work log data
Open the issue, check the work log date and click pencil.
Edit the work log date to the correct date.
Was this helpful?