Kanban team burnup

Why use Kanban team burnup

How to configure

The configuration settings are split into three categories. Each category is displayed as a separate tab:

  • Burnup

  • Issues

  • Forecast

Burnup settings






The name of the Kanban board is displayed on the gadget view as a link to the board. Using Title option you can define a custom name for the link.

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.

Kanban board

Issues statistics of the selected Kanban board is displayed on the chart.

Estimation field

Available options are:

  • Story points

  • Time Estimate

  • Issue count

  • any number field available in Jira, e.g. Business value

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:

  • Hours

  • Days - number of hours per day is based on Jira Time Tracking configuration

Reporting period

The reporting period defines the date interval for the report.

Available options are:

  • This week

  • Last week

  • This month

  • Last month

  • Past 30 days

  • Past 90 days

  • Interval count

Interval count

This option is available when the Reporting period = Interval count.

Grouping interval

The grouping interval defines how issue metrics are grouped.

Available options are:

  • Daily

  • Weekly

  • Bi-weekly

  • Monthly

Value labels

Annotate all sprint metrics with their number values on the chart.

Issues settings






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.


Filter issues by selected releases.

Using this option you can create Release velocity report grouped by intervals.


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.

Forecast settings

In this section, you can adjust how the completion forecast is calculated.

By default, the forecast is calculated for the following velocities:

  • Max velocity

  • Average velocity

  • Min velocity

Those velocities are automatically calculated based on the last completed sprints. The number of completed sprints is defined in the Sprint count option.

As values and complete dates of the built-in velocities are calculated automatically their values are displayed as 'auto'.

The completion date can be calculated based on a custom velocity value.

If you provide the desired completion date the required velocity to achieve that goal will be calculated.





Interval count

The number of intervals to calculate Min, Max and Average automatic velocities which are used in forecast calculation.

Remaining work

The remaining work is automatically calculated as a sum of all not completed issues.

You can adjust this value to check how it affects the completion date.

Remaining work growth per interval

Change remaining work amount on an interval basis to simulate scope change in the future.