Sprint burndown
Why use Sprint burndown
How to configure
The configuration settings are split into two categories. Each category is displayed as a separate tab:
Burndown
Issues
Burndown settings
Title | The name of the Agile board is displayed on the gadget view as a link to Velocity Chart report of that board. Using Title option you can define a custom name for the link to the board. This can be useful if you have several gadgets based on the same agile board with different configurations for sprints, dates, issue filters or other gadget parameters. |
Scrum board | Active sprints of the selected Scrum board are displayed in the Sprint option. |
Sprint | Burndown chart is displayed for the selected sprint. |
Estimation field | Available options are:
When the board is selected the estimation field is set to board's estimation statistics from its configuration. You can change the default value to any other available estimation if needed. |
Time unit | Available when estimation field is set to Time Estimate. Time values can be displayed in:
|
Forecast velocity | The forecasted complete date is calculated for the enabled automatic velocities. |
Days count | The number of days which are used to calculate Min, Max, Average velocities in Forecast velocity option |
Value labels | Annotate all sprint metrics with their number values on the chart. |
Issues settings
Sub-tasks | In all Jira Software reports sub-tasks are not included into velocity, burnup, burndown statistics. Using this option you can include sub-tasks into sprint metrics calculation. |
Releases | Filter sprint issues by selected releases. Using this option you can create Release velocity report on sprints basis. |
Epics | Filter sprint issues by selected epics. Using this option you can create Epic velocity report on sprints basis |
JQL filter | Filter sprint issues by custom JQL criteria. Using this option you can create a velocity report for any custom Scrum board scope. |