Kanban team velocity
Why use Kanban team velocity
Track progress of Kanban teams on a project, epic, release or custom scope level using quick issue filters.
By default, the progress is calculated based on issues of the last board column, but you can configure source and target columns to get progress at any stage of the workflow.
Choose estimation statistics from Issue count, Time Estimate, Story Points.
How to configure
The configuration settings are logically grouped into categories. Each category is displayed as a separate tab:
Velocity
Issues
Velocity settings
Title | The name of the Kanban board is displayed on the gadget view as a link to Control 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 Kanban board with different configurations. |
Kanban board | Statistics based on issues of the selected board will be displayed on the chart. |
Estimation field | Available options are:
|
Time unit | Available when estimation field is set to Time Estimate. Time values can be displayed in:
|
From column | Calculate issue statistics if issue workflow source status is mapped to this column. |
To column | Calculate issue statistics if issue workflow destination status is mapped to this column. |
Reporting period | The reporting period defines the date interval for the report. Available options are:
|
Custom dates | This option is available when Reporting period = Custom dates. |
Interval count | This option is available when Reporting period = Interval count. |
Grouping interval | The grouping interval defines how issue metrics are grouped. Available options are:
|
Average | Average for interval metrics can be calculated based on all visible intervals or as a moving average based on a specified number of intervals. Available options for moving average are: 2, 3, 4, 5 intervals |
Chart type | Available chart type options are:
|
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 issues by selected releases. Using this option you can create Release velocity report grouped by intervals. |
Epics | Filter issues by selected releases. Using this option you can create Epic velocity report grouped by intervals. |
JQL filter | Filter sprint issues by custom JQL criteria. Using this option you can create a velocity report for any custom Kanban board scope. |