The 8.0 app version is released only on the Cloud platform. The Data Center release is scheduled for the end of June.

Content:

Getting Started Page and Chart Catalog

Historically, every new data source was introduced by adding a new entity to the chart catalog, which helped identify new capabilities and visually identify what changed. However, as we plan to continue adding new charts and now have a long list of different data sources, that approach appears not to be scalable.

Instead of different charts for different data sources, now you have three charts under the Create chart button:

Open

Open

The data source type will be selected on the next step in the flow.

Chart Templates

Alongside streamlining the process of adding new chart types, we’ve also introduced a new way to discover chart features—by combining them into templates tailored to Agile teams' most common use cases.

Whether you start creating a chart from the dashboard (by adding a gadget) or the app page, you’ll land on the Getting Started Page, which features a navigation menu and a template catalog.

Open

Open

 

A template is simply a chart with preselected settings that you can adjust however you like. To start creating a chart, just click the button that appears when you hover over the template cover.

Open

If you're not sure which template is right for you, you can always start with the default chart creation option:

Open

New Data Sources

When you create a chart, the first step is to add a data source—the entity in Jira that defines which issues will be used to calculate the data visualized on the chart.

There are new data sources available to help you visualize delivery data directly on your dashboards:

Open

Open

Jira Projects

Open

Use this when you need to track progress across one or several projects.
Tip: Use breakdown by project to understand the dynamics separately.

Releases

Open

Allows you to track throughput for one or multiple releases.
Tip: Use breakdown by release to understand the dynamics separately.

Issue hierarchies built on the Parent field relationship

Open

Track the progress of Initiatives, Features, or Solutions. Set the parent issues and specify the level of depth where the issues contributing to throughput are located.

Issue hierarchies built on issue links and Epics

Open

Use this when your hierarchy is built on custom issue types above Epics, and you want to track their child issues. Specify the issues that represent your Initiatives, Program Epics, etc., and set the depth to Epic to calculate velocity for all their child issues.

Epic static list

Open

If you need to monitor key Epics, simply select them using the multi-select input.
Tip: Use breakdown by Epic to understand the dynamics separately.

Epic dynamic JQL condition

Open

Use this to maintain a dynamic list of Epics, for example, those created during a specific PI. Set a condition to automatically include matching Epics, ensuring the chart updates as new ones are added.
Tip: Use breakdown by Epic to understand the dynamics separately.

Saved or custom JQL

Open

Use this when you need maximum flexibility in defining the issues to include. Extended JQL filters provided by other Jira apps (e.g., Scriptrunner) can also be used.

Pre-selected data sources for particular templates

When using a particular template, some data source types might not be available during the initial chart setup, but you can still change them once the chart is loaded:

Open

Enhanced chart editing experience in Velocity and Burnup/Burndown charts

Once you select a data source, chart editing continues in a full-screen modal where you can adjust settings and instantly see changes reflected in the chart, breakdown, and issue list—eliminating the need to switch back and forth between settings and the chart view each time you make a tweak:

Open

Settings are organized by their impact: on the chart, breakdown, issue list, and general settings. These are further grouped into sections such as Data Source, Calculation, Issue Filter, and User Filter:

Open

The right-hand panel can be collapsed, giving you a full-screen experience to explore the chart and data in detail:

Open

Open

You can save the chart to any existing dashboard or create a new one directly from this view:

Open

Issue type filter

The updated version of the issue type filter allows you to select specific issue types to be included in chart calculations, giving you a much more granular level of configuration. For example, after selecting a project, you can define whether you want to include Epics, Stories, or Sub-tasks from that project:

Open

Revised Release Filter

Navigating different fixVersions with the same name across multiple projects is now easier. First, you select the project and then choose one or several fixVersions you want to see on the chart.

Open

Issue list configurable columns

The issue list is often useful for visually investigating specific segments in your metrics, but it previously lacked the flexibility to show more detailed data. That’s now been addressed—you can add any columns you need from your issue layout fields to customize the list to your needs:

Open

New features and improvements in Velocity charts

Updated Rollover metric calculation approach

We received much feedback about the Rollover metric and have developed a new version. Now, it is defined as issues that were in a previous sprint and were added to the current sprint. This approach better reflects the nature of rollover—moving work from one sprint to the next.

Open

However, we recognize that a metric showing issues present in multiple sprints is also valuable. So we've slightly revised it and kept it in the issue list. This allows you to investigate which issues appear in multiple sprints (even if they’re not officially marked as rollover).

The issue list now displays the number of sprints each issue has been part of. You can hover to see details, sort to identify outliers, and even apply a breakdown based on these values.

Updated the Custom Done statuses calculation approach

Previously, we used a very straightforward logic that let you select multiple “Done” statuses to count issues as completed once they reached any of those statuses. For example, if you had two statuses—Done and Deployed—both reflecting that a story is completed, selecting both would tell the chart to count an issue as completed if it was in either status.

However, if an issue reached one of those statuses in one sprint and the other in the next, it was mistakenly counted twice, making that setup ineffective.

Starting with this version, the chart will count such issues only once. You can now confidently select multiple “Done” statuses, and the issue will be counted as completed as soon as it reaches any one of them, without duplication across sprints.

New features and improvements in Burnup/Burndown charts

Total work metric

When you have a fixed scope of work—like a release, epic, program, or initiative—it’s important to track how that scope changes over time. This helps make forecasts more realistic and manage the team’s process to avoid unnecessary scope creep.

Open

Remaining Work (Scope) Change Trend

By default, the remaining work growth configuration is set to 0 to provide a forecast based on the current scope volume.

Open

Now, you can remove this value to see how the remaining work growth trend—calculated from previous history—affects the delivery date. Ensure that you set enough intervals from the past to build the trend.

Open

Open

This feature helps you model real-world scenarios where scope increases over time, making your projections more realistic.

Forge and Runs on Atlassian

We proudly announce that this release brings the Agile Reports & Gadgets app into the Runs on Atlassian program, as the app has migrated to the Forge platform and now meets the highest standards set by Atlassian.

In simple terms, this means:

1. Your data stays with Atlassian – All data used by the app is processed and stored within Atlassian’s trusted cloud infrastructure, never leaving the Atlassian environment.

2. Stronger security and privacy – The app now adheres to the same security, compliance, and data protection standards as Atlassian Cloud products, giving your team peace of mind.

3. Simplified data residency – App data follows the same residency rules as your Atlassian products, helping you meet local compliance and regulatory requirements more easily.

4. Streamlined approvals – IT and security teams can confidently approve the app without needing to vet an external hosting provider, speeding up procurement and governance.

5. Improved reliability and performance – Running directly on Atlassian’s infrastructure ensures a seamless, fast, and stable experience aligned with the performance of your other Atlassian tools.

This marks a major step forward in trust, compliance, and simplicity for all our users.