Jira dashboard gadgets —
for release burnup and scope change

Ten dashboard gadgets built around Jira versions: release calendar, release roadmap, countdown, release progress bar, universal progress bar, release status report, scope change report, release burnup and release trends on the Standard edition, plus the release frequency report on Advanced. Most of them combine versions from several projects, so a release that spans teams is reported as one.

Jira’s release burndown and version report are reports on a Scrum board, for one version at a time, and they are not among Jira’s pre-installed dashboard gadgets. Release Gadgets answers the same questions on a dashboard: the release burnup gadget shows done work against total scope for one version or many and, on Jira Cloud, a projected release date; the release status report shows each version’s progress and dates.

Out of the box, Jira’s sprint report marks issues added after a sprint starts, and the release burndown shows work added to one version. For a release that spans several versions or projects, add the Scope Change Report gadget: it lists every issue added to or removed from the chosen versions in a period you set, with the change measured in the estimate field you pick. The Release Trends gadget shows the same change over time against completed work. See the Scope Change Report documentation.

Yes. The Release Calendar gadget puts versions from one or many Jira projects on a month view by release date, unreleased in blue and released in green, with archived versions in or out. Click a release to open it in Jira. On the Advanced edition it also shows the epics and sprints that feed the release. Jira’s own Calendar gadget shows work items by due date, not versions.

Add the Release Roadmap gadget and pick the projects and versions. Each version becomes a bar from its start date to its release date, one swimlane per project; a version with no start date shows as a milestone, and hovering a bar shows its dates and progress. On the Advanced edition, add epics by their date fields and team sprints as lanes of their own.

Add the Release Progress Bar and choose one version or several, from one project or many. It shows how many issues are in To Do, In Progress and Done, with percentages, plus the earliest start date and the latest release date of the chosen versions. Every number opens the matching issues in Jira, ready to export or change in bulk.

Yes, with the Universal Progress Bar. Enter any JQL, such as every issue in a release, the stories in an epic or the sub-tasks of a task, and it shows how many are To Do, In Progress and Done. Custom workflow statuses are matched to those three status categories, and every number opens the issues in Jira.

Use the Release Status Report gadget. It shows the combined progress of all chosen versions on top and, for each version, its status, progress, start date and release date, from one project or many. Sort by any column, and hover a progress bar for its done, in progress and to do counts.

Yes. The Release Burnup gadget charts total scope against completed work for many versions combined and for each one, in story points, hours or issue count. Narrow it with a saved filter, for example, to stories only.

Yes, with the Release Trends gadget. Per day, week or month it draws scope added or removed as one line and completed work as another, for the whole release and for each version. Reopening done work pulls the completed line down; re-estimating open work moves the scope line.

Add the Release Frequency Report: Advanced edition on Jira Cloud, included on Data Center. Pick projects or whole project categories and a period; it counts releases per interval, can include unreleased and archived versions, and draws a trendline. Click a bar to see the releases behind it. Release frequency is an important part of DORA metrics.

Yes. The Release Countdown gadget shows the days, hours, minutes and seconds left until the release date of the version you pick. Put it on a team dashboard or a wallboard so the date stays in sight.

Yes, with a different route on each platform. On Jira Cloud, Confluence doesn’t embed third-party gadgets directly, so put the gadgets on a single-column dashboard, open it in wallboard mode and add that address to the page with an iFrame macro. On Data Center, Atlassian removed built-in gadget embedding from Jira 10 and Confluence 9.2 and offers a replacement macro; we tested every Release Gadgets gadget with its beta. Step by step: Exporting gadgets to Confluence.

Yes, from one Marketplace listing. On Data Center it supports Jira 10 and 11 and includes every Advanced feature. On Jira Cloud you choose the Standard or Advanced edition, and the Cloud app runs on Atlassian’s own infrastructure.

Standard has the nine core gadgets and is free on Jira Cloud sites with up to 10 users. Advanced adds epics and sprints on the roadmap and calendar, and the release frequency report, and is paid from the first user. Above 10 users, both are licensed for the same user tier as your Jira site — that is how the Atlassian Marketplace licenses every app, not a rule specific to us. Data Center runs the Advanced edition, with licenses from 50 users. You can start a free 30-day trial of either edition, without a credit card, and switch editions during or after it. On Jira Cloud, Advanced is $8 a month for up to 10 users; Data Center starts at $394 a year for 50 users. Every user tier is on the Marketplace pricing tab.

Not necessarily. Release Management has its own dashboard gadgets, built around its release boards; with both apps installed you will see two similar sets, with different icons and names. Release Gadgets needs no release boards: it works on plain Jira versions, so it suits teams that want release reporting without changing how they plan. For release workflows, approval gates and release notes as well, see release management for Jira.

Yes. On Jira Cloud it runs on Atlassian’s infrastructure and is Cloud Fortified. It takes part in Atlassian’s Marketplace bug bounty program on Cloud and Data Center, is declared on its listing as not storing personal data, and is covered by SOC 2 Type II. For a security review, send our Trust Center — compliance, sub-processors and data handling in one place.