Sprint burndown chart showing active sprint estimation to the future sprint end date
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
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:
project = <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:
