JIRA Agile 6.6.70 changes the terms "Plan mode", "Work mode", and "Report mode" to "Backlog", "Active sprints"/"Kanban board", "Reports" respectively. For more information, see the JIRA Agile 6.6.70 release notes.

Skip to end of metadata
Go to start of metadata

(info) Note that this page only applies if you are using the Classic Boards (which are no longer being actively developed; read more).

On this page:

Aggregate Hour Burndown Charts

An aggregate hour burndown chart is generated for JIRA Agile versions with one or more child versions. However, the logic in generating these charts is different to that of sprint hour burndown charts. For aggregated charts, the Remaining Estimates and Team Effort of each child version's sprint chart is summed and spread across the entire duration of the parent version's aggregated chart.

Initial Number of Hours

The initial 'Number of Hours' values (at x=0) of the Remaining Values curve (green) and Guideline curve (red) in an aggregate hour burndown chart are the sum of the initial 'Number of Hours' of the respective green and red curves of its sprint charts.

Unlike sprint hour burndown charts, the initial 'Number of Hours' values on aggregate hour burndown charts can vary, since it is common practice to perform sprint planning immediately before the sprint's start date (as the previous sprint is winding up).

After planning the first sprint, the initial 'Number of Hours' values of the aggregate hour burndown chart's red and the green curves will match those of the first sprint, even if the start dates differ. Once the second sprint is planned, its initial values will be added to the aggregated chart's initial values. Hence, the starting points (x=0) of the red and green curves will move up.

Drawing changes


  • After sprint planning on two sprints, the first of which starts on the 19th of July with 10 hours worth of estimated work and the second starting on the 22nd of July with 20 hours of work, the initial 'Number of Hours' values of the sprint's aggregated chart is 30 hours. On the 20th of July, 5 hours of work are logged, which is reflected in the green curve on that date.

Sprint periods usually occur back to back. However, it is possible for time gaps to occur between them. If work is logged outside the time period of any sprint, but during a valid date within the time period of its parent version, then that work log will be ignored in the parent version's aggregate hour burndown chart.