Loading...

XML

Word

Printable

The Burndown Chart is not summing up the subtasks estimation when using Original Time Estimate set on the board.

Jira Software Cloud

Create a classic Scrum project
Access the estimation configuration on the board and set it to Original Time Estimate
Create some stories and add subtasks to them
Add time estimation to the stories and subtasks
Create a sprint, add the stories created to the sprint and start it
See the Burndown chart

According to the Burndown chart documentation, the expected behavior is:

Subtask behavior when remaining estimate and time spent is enabled	Subtask behavior when remaining estimate and time spent is disabled
If you add a subtask to an issue that's already in an active sprint, the subtask is treated as scope change. The scope change is also indicated in the Burndown Chart.	If you add a subtask to an issue that's already in an active sprint, the subtask is also treated as scope change. However, scope change is not indicated in the Burndown Chart for the subtask.
Time estimates of subtasks are rolled up to the parent task. This means that the parent task will have the total sum of all remaining estimates of the subtasks.	Time estimates are tracked individually across the subtasks and the parent task itself.

The actual results are:

If you select the option "Original Time Estimate" as a parameter in the Burndown chart report, the subtasks are not displayed and their estimation is not summed up to their parent issue, independently if the option "Remaining Estimate and Time Spent" is enabled or not
When the "Remaining Estimate and Time Spent" is enabled, the Burndown chart shows another parameter, "Remaining Time Estimate". If you use this parameter in the report the subtasks are displayed individually in the report.

Currently there is no known workaround for this behavior. A workaround will be added here when available

is related to

JSWCLOUD-6007 Burndown chart doesn't take under consideration the sub-tasks estimation