---
title: "Release Trends Gadget"
canonical: "https://help.releasemanagement.app/space/GFJR/1521254818/Release%20Trends%20Gadget"
format: markdown
---
> Macro (include)
# Summary
> Macro (details)
>
> | **Image** |  |
> | --- | --- |
> | **Name** | Release Trends |
> | **Summary** | Show cumulative and individual releases trends |
> | **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 “Trends“ to find it
# What it’s about?
Trends gadget depicts “scope change” and “done items“ velocity trends for release.
- **Cumulative** - as a summary of all versions you picked up
- **and Individual **- for each and every versions 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?
Move the mouse around the graph area to see details for specific dates.
# How it works?
In trends gadget, we calculate the number of items *added *or *removed *from the release (**Grey **Line) on a daily/weekly/monthly basis and track the trend of completed versus reopened items (**Blue **Line).
The calculation includes the following events:
- **Work item entry or exit from the release:**
- If an item enters the release in the [TODO] or [In Progress] [status categories](https://support.atlassian.com/jira-cloud-administration/docs/what-is-a-workflow-status/), we count it as newly added scope, increasing the **Grey **Line.
- If an item is added to the release with a status in the [Done] category, we count it as both newly added and completed scope, increasing both the **Grey **and **Blue **lines.
- The same approach applies to removed items, which decrease the values for the **Blue **and **Grey **lines, potentially making them negative.
- **Completion or reopening** of an item (moving from [TODO] or [In Progress] categories to the [Done] category):
- Completion increases the **Blue **line.
- Reopening decreases the **Blue **line.
- The **Grey **line remains the same.
- **Re-estimating**, if the chart is based on estimates rather than issue count:
- Changing the estimate for the [Done] category items changes both the **Grey **and **Blue **lines.
- Changing the estimate for [TODO] or [In Progress] category items only affects the **Grey **line.
# What are the configuration options?
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. **Group by** - show daily, weekly or monthly trend
5. **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.
6. **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.
7. **Done items** - do you want to show done items (aka velocity) trend alongside scope change?
8. **Scope change **- do you want to scope change trend impacting your projected release date along side done items trend?
9. **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.
10. **Show version summary **- toggle to check if you also want to add a progress bar for your releases, both cumulative and individual
11. **Auto refresh** - automatically refresh the gadget
> Macro (include)