---
title: "Release Burn-up Gadget"
canonical: "https://help.releasemanagement.app/space/GFJR/1521254645/Release%20Burn-up%20Gadget"
format: markdown
---
> Macro (include)

# Summary

> Macro (details)
> 
> | **Image** | ![image](media://10bd751c-c5bb-4f04-8e0b-7ae28144812a) |
> | --- | --- |
> | **Name** | Release Burn-up |
> | **Summary** | Show cumulative and individual releases burn-up |
> | **Category** | Releases Insights |
> | **Hosting Types** | [CLOUD], [DATACENTER] |
> | **Advanced Features?** |  |

# Topics

> Macro (toc)

# How to find?

Open your favorite Dashboard or create a new one. Click on “Add gadget“. Search for “Burnup“ to find it

![image](media://c100a4fe-9c7f-478d-a76c-23dcd6041ce5)

# What it’s about?

Release burnup gadget outlines incremental value gained or efforts burned for your releases, namely

- **Cumulative** - as a summary of all releases you picked up
- **and Individual **- for each and every release selected

It is recommended to use the gadget to understand the progress through out the release, also measure impact of burn rate and possible scope creep to projected release date. 

# How it looks?

![image](media://71eb59e0-d76c-4a5d-bce8-5d38a1839c3a)

Move the mouse around the graph area to see details for specific dates.

# How we calculate projected release date?

[CLOUD]

> 📝 If **start date is defined **and **at least 30% of release scope is completed **we will calculated projected release date and outline the guideline on the chart.

How we calculate the % of the work completed?

> **[% of the work completed] = % of **( [all issues in all versions with status category **Done**] + <span style="color: #bf2600">**50% of **</span>[all issues in all versions with status category **In Progress**] ) / [all issues in all versions]

If **[% of the work completed] **is >30% and <100% we will calculate Projected Release Date as following:

> **[projected release date] = **[start date] + **[projected days in release]**

where

> **[projected days in release] = **(** **[today] - [start date] ) / **[% of the work completed]**

*In essence, we evaluate today’s progress and, assuming the current velocity remains constant, estimate the time needed to reach full completion.*

Because the calculation involves a degree of approximation, we typically include a 10–15% uncertainty buffer on both sides of the projected release date.

# What are the configuration options?

![image](media://59aefb86-16c9-4cb4-a434-73c045dcceb2)

The gadget has the following configuration options:

1. **Name **- caption to outline
2. **Projects **- multi-select of projects that become a source of your versions / releases
3. **Versions **- a multi-select of versions / releases from the selected projects
4. **Units - **pick up the measure units. We support Story points, Hours and Issue Count. Story points for the value gained, Hours for efforts burned, Issue count is in the middle. All three supported cross Classic and Next-Gen type of projects for Jira Cloud.
5. **JQL filter - **further tailor your burn up by predefined JQL filter to shortlist Jira issue you want to use as data source for the graph. The classical use cases are additional filtering by IssueType.
6. **Draw from start date - **starts the graph from release start date (or earliest start date of multiple release selected). Otherwise from first unit value change.
7. **Show version summary **-  toggle to check if you also want to add a progress bar for your releases, both cumulative and individual
8. **Auto refresh** - automatically refresh the gadget

> Macro (include)