Sprint Report - completed issues do not burn down the total Sprint estimate
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
When viewing the Sprint Report in Jira Software the completed issues estimates don't burn down over time. In the example below, the red line represents actual work done during the sprint — it's drawn from the total estimate of the issues at the start of the sprint, and it goes higher or lower as your team works on the issues in the sprint. If the team has completed some of the estimated issues during the sprint, and red line still does not burn down. However, newly added issues to the sprint still register as scope increases.
Environment
Jira
Diagnosis
The following points need to be checked:
Issues completed during the sprint were estimated.
The board is set to use the correct "Estimation Statistic" and it has not changed recently.
The issues worked during the sprint are included in the Board filter.
The last column of the board correctly maps the "Completed" workflow status of the issue and the resolution is properly set.
Both of the below post-functions exists in the workflow transition that sets the issue to the "Completed" status
Class: com.atlassian.jira.workflow.function.issue.UpdateIssueStatusFunction
Set the issue status to the linked status of the destination workflow step.
Cause
If #1 - #4 have been checked and are configured correctly, then the issue is caused by #5, the workflow post-functions in the workflow transition that leads to the status mapped to the last column of the board. This is usually the "Done" column or similar.
For this to happen, the issue workflow needs to be affected by the bug JSWSERVER-11547: JIRA Agile Simplified Workflow - Post Functions displayed incorrectly (fixed in Jira Software Server and Data Center 9.0.0). In this case, the user can add a duplicate post-function "Set issue status to the linked status of the destination workflow step.". Here is an example:
These two post-functions are actually the same (duplicate), so it's only necessary to have one of them:
Class: com.atlassian.jira.workflow.function.issue.UpdateIssueStatusFunction
Set the issue status to the linked status of the destination workflow step
Solution
In order to resolve the issue at hand, please delete the duplicated post-function that is setting the issue status. This in turn will fix future problems with issue status for issues completed during the Sprint, and the Sprint Report will work properly.
Create a workflow draft.
Delete the duplicated post-function from the transition. The post-function that's referencing class "com.atlassian.jira.workflow.function.issue.UpdateIssueStatusFunction".
Save a workflow backup and publish the new workflow.
For additional information please refer to the following article:Advanced workflow configuration
Was this helpful?