The Release Burndown chart functions like the Iteration Burndown chart with additional features.
Based on your settings, the to do series (blue line) burns down story points or counts. Likewise, the accepted series (green line) burns up story points or counts. The ideal (black) line is the maximum number of points defined in the release or iteration. Accepted stories have a schedule state of Accepted or greater.
The prediction series is only shown in active releases. It includes an advanced algorithm to help teams predict when their release and iterations will complete. The algorithm looks at the most recent stable velocity (slope of the accepted series) and the current scope to project the most likely time when the current scope will be completed. The sophistication of the algorithm is in how it picks the recent stable period.
You can zoom in or out on the chart to get a better view of your release. Use the - and + buttons on the zoom bar to adjust your view. The default zoom factor is from months to weeks. You can adjust the zoom factor from years to quarters and from weeks to days.
The chart is scoped to global project settings. On scoped dashboards or custom pages, the chart follows the scoping of the page. Select the Children checkbox from your global project picker to include stories from child projects.
When the Release Burndown is added to a page, the settings view displays by default. The settings options specific to this chart are:
The chart shows progress for a chosen release by default. You may also view the burndown for a single iteration.
The chart burns story points (Story Plan Estimate) down by default, but you can display burndown by story count. Story Plan Estimate is a relative, abstract value that represents overall team effort. Story Count is the actual number of stories.
The to do and accepted values are depicted as a line by default. You can display those values as columns.