Viewing the Release Burndown
Screenshot: Example Release Burndown report (story points)
About the Release Burndown report
The Release Burndown report shows you how your team is progressing against the work for a release. In JIRA, there is no "release" entity — a version is equivalent to a release (hence, the term "version" will be used instead of "release" in this document). The report will show data based on the estimation statistic that your board is using.
Here are some of the ways that you could use a Release Burndown report:
- See how quickly your team is working through the backlog
- See how work added/removed during the sprint has affected your team's overall progress.
- Predict how many sprints it will take to complete the work for a version, based on past sprints and changes during the sprints.
If you have used the Version Report before, you will notice some similarities, however the Release Burndown is optimised for scrum teams who work in sprints and makes tracking much easier.
Viewing the Release Burndown report
To view the Release Burndown report for a version:
- Navigate to the desired board.
- Click Reports.
- Select Release Burndown from the Reports dropdown at the top of the page.
- Choose the desired version from the dropdown next to the Release Burndown header. You will be able to choose from versions that are in projects configured for your board (via the board's filter).
Tip: Click How to read this chart at the top of the chart to view a short description of the Release Burndown report.
If you are using Internet Explorer 8, the Release Burndown will not work.
Printing the Release Burndown report
To print the report, view the report and use the print functionality for your browser. The report will fit to either A4 or Letter-sized pages in both portrait and landscape (note, there is a known issue printing in landscape using Chrome).
Understanding the Release Burndown report
Before you start using the Release Burndown report, you should get to know how it works.
The sprint bar
- Light green section = work completed during the sprint.
Note, if a bar is completely light green, you won't be able to tell how much of the work completed was originally estimated or not. To find out this information, click the bar to view the details.
- Light blue section = work that is remaining in the version, out of the total work estimated for the version at the start of the sprint.
- Dark blue section = work that was added during the sprint, but not originally included (i.e. scope change).
- Light green section + light blue section = total work in the version, that was originally estimated at the start of the sprint.
- Light blue section + dark blue section = total work in the version, that is remaining at the end of the sprint.
- Bars with grey sections = predicted sprints (see below).
Predicted sprints are calculated based on your team's velocity* (amount of work completed in the last three sprints) and the total work remaining in your backlog. Scope change is not considered when calculating the velocity*, but is included in the total work remaining.
* not the same as the velocity described in the velocity chart.
Consider the following example:
- Assessing the outstanding work: 26 story points are remaining for the version, at the start of the current sprint (sprint 5).
Note, the "22 remaining (story points)" label (at the top of every Release Burndown report) subtracts the 4 story points that are predicted to be completed in the current sprint.
- Calculating the velocity: 11 story points were completed in the last three sprints (sprint 2, sprint 3 and sprint 4). This averages out to a velocity of 4 story points per sprint, rounding to nearest story point.
- Predicting the remaining sprints: At a velocity of 4 story points per sprint, it will take 7 more sprints (including the current sprint) to complete the work for the version: 26 story points. That is, 6 sprints of 4 story points plus one final sprint of 2 story points.
The current sprint is usually not counted when calculating the team's velocity. In the example above, the current sprint bar shows grey sections (like the bars for the predicted sprints) to represent this. The exception is when you have already completed more work in the current sprint than the work that was predicted to be completed. In this case, the current sprint (and the actual work completed) is used as one of the three sprints used to calculate the velocity. Also, the sprint bar will show green/blue sections, like the bars for completed sprints.
For example, in the chart above, if your team had already completed more than 4 story points in sprint 5, then the work completed in sprint 3, sprint 4 and sprint 5 would be used to calculate the velocity, rather than sprint 2, sprint 3 and sprint 4.
The following questions and answers cover the other key functionality in the Release Burndown report:
The Start date and Release date configured for the version are shown on the bottom of the report as the Planned start date and Planned end date. However, these are planned dates and they do not determine the first and last sprints shown on the report.
- The first sprint shown is the one that contains the first issue (in the version) that transitions out of the To Do status, i.e. work is started on the version.
- The last sprint shown is the one when all work is completed for the version; or if work remains, then the predicted sprint when work will be finished.
The mapping of statuses to your board determines when an issue is considered "To Do" or "Done". See Configuring Columns for more information.
The Release Burndown report can only make predictions based on the estimated issues in your version. If you have a high percentage of unestimated issues, then the predictions in the report will not be reliable (the % unestimated issues label is coloured red when the percentage is above 30%, to help make you aware of this).
For example, if you have only estimated 10% of the issues in the version, then the report predict the completion of work for the version based on the 10% of the total issues. In reality, your team probably has much more work left to complete.
- An issue in a version (before it started) is estimated (estimate is added)
- An issue in a version (before it started) is re-estimated (estimate changes)
- An issue is added to a version (after it was started) with an existing estimate
- An issue that was added to a version (after was it started) is estimated (estimate is added)
- An issue that was added to a version (after was it started) is re-estimated (estimate changes). Note, if the issue is re-estimated in a later sprint, the scope is retroactively adjusted in the sprint that the issue was originally added to.
- The issue will not be shown in the earlier sprint.
- The scope will remain unchanged and the work completed is still shown.
- The scope will remain unchanged.
- The issue will be shown on the report, as if it was always part of the version.
If your issue is in an unmapped status (i.e. status not mapped to a column), it will not be considered in the Release Burndown chart. That is, it won't be included in the sprint bars, the % unestimated issues, remaining story points, etc.
In the 'Completed Issues' table, an issue is grouped into a sprint if its completion date falls after the start date of the sprint and before the start date of the next sprint, regardless of whether it was assigned to the sprint during planning.
For example, consider the following sample data:
- Sprint 1 — starts on July 1 and ends on July 14
- Sprint 2 — starts on July 17 and ends on July 30
Say issue 'ABC-123' was assigned to Sprint 1 during planning, but was not completed until July 18. In the 'Completed Issues' table, ABC-123 would be grouped under Sprint 2, rather than Sprint 1. This is a more accurate reflection of what happened during the release and helps maintain the integrity of the report data.
If you encounter an issue that is not on this list, please raise it in our issue tracker.
Was this helpful?
Thanks for your feedback!