We’re excited to announce the release of Agile Reports and Gadgets 8.0, launched on June 19, 2025 - a major app and user experience upgrade that reshapes how you build and read Jira analytics. This release also marks our first step toward achieving the Runs on Atlassian badge by moving the app to Forge, unlocking stronger security, simplified operations, and native cloud scalability.
With an updated UI across nearly every screen and workflow, this release sets the foundation for faster chart building, smarter filtering, and more intuitive navigation. The new features include:
WYSIWYG editor - change settings and instantly see the chart
Chart templates - quickly get started with popular use cases
New data sources - visualize delivery and team performance your way, with more flexibility in reporting
Fine-tuned Issue type filtering - include only the issue types you need to get cleaner, more relevant chart metrics
Simplified Multi-project release filtering - focus only on the shared scope across projects when fixVersions match
Issue list with configurable columns - fully customize the view by adding any columns from your issue layout
Improved Rollover metric - accurately track work that carries over between sprints
Refined “Done” status logic - avoid double-counting and make reporting more precise
Total work metric – see how your team’s scope evolves over time
Scope trend tracking - improve forecast accuracy by accounting for historical scope growth
Whether you're an Agile project manager, Release train engineer, Scrum master, or Product manager, Agile Reports and Gadgets 8.0 is built to support how you plan, track, and forecast software delivery.
So, what exactly is new in Agile Reports and Gadgets 8.0?
Let’s take a look at the highlights that make this release our biggest and most user‑focused update yet 👇
We’re pleased to announce that the Agile Reports and Gadgets app now runs on the Forge platform, marking the first major step toward Runs on Atlassian certification.
Our target for full certification is September 1, 2025, and the app already benefits from the platform’s built-in security and reliability.
Here’s what it means for your team:
Your data stays within Atlassian - All processing happens inside Atlassian Cloud. No external services. No extra risk.
Stronger security & compliance - The app now follows the same strict rules as native Atlassian products.
Simplified data residency - Your app data stays where your Jira instance is. No extra configuration needed.
Faster procurement & approval - No external hosting to review. Your security team will thank you.
Better reliability - Hosted by Atlassian. Maintained by Atlassian. Scales with Atlassian.
This is a huge step forward in trust, simplicity, and enterprise-readiness. And it’s already live 🎉
Now, no matter which Agile Reports and Gadgets chart you’re editing - Velocity Charts, Cycle Time Charts, or Burnup Burndown Charts - every setting you change instantly updates the chart view. See the effect of your configuration choices right away, with no need to switch tabs or reload anything (Velocity chart example is shown, other charts have the same UX):
As you tweak any setting - be it chart, breakdown, issue list, or global - the chart updates instantly, so you always see the impact in real time.
Settings are neatly grouped into intuitive categories like Data source, Calculation, Issue filter, and User filter to help you stay focused.
Need more space? Just collapse the right-hand panel. Ready to share? Save your chart as a gadget to an existing dashboard - or create a new one without leaving the screen.
To help you build insightful charts even faster, Agile Reports and Gadgets 8.0 brings a full Chart template catalog.
Each template is a pre-configured chart tailored to help you get started with popular use cases in seconds. Whether you’re analyzing delivery accuracy or planning predictability, you can spin up a ready-to-go chart in just a few clicks. Here are some examples of what you can visualize instantly:
Start from the dashboard or app page - you’ll land on the Getting started page with a template catalog and quick navigation. Just hover over a template and hit Create chart (➊) to adjust and publish:
Don’t know which one to choose? You can still start from scratch with a default config and fully customize from there (➋).
When creating a chart, it all starts with the data source - the Jira entity that defines which issues will be used to calculate the data visualized on the chart.
In Agile Reports and Gadgets 8.0, we’ve expanded the list of available data sources to give you even more flexibility in how you visualize delivery progress and team performance right inside your Jira dashboards:
Jira projects
Releases
Issue hierarchies built on the Parent field relationship
Issue hierarchies built on issue links and Epics
Epic static list
Epic dynamic JQL condition
Saved or custom JQL
Pre-selected data sources for particular templates
Let’s take a closer look at the new data sources that unlock more flexible and powerful charting options.
🔸1. Jira projects
The new Jira Projects data source lets you visualize progress and delivery metrics across one or multiple projects - all in one chart.
📊 Availability in charts:
Agile Velocity Chart Gadget: Cross-team, Individual (Benchmarking - coming soon)
Agile Cycle Time Chart: Histogram, Trend, Time in Status - coming soon
Agile Burnup Burndown Charts: Burnup, Burndown - coming soon
💡 Tip: Use the breakdown by project feature to compare project-level trends side-by-side and uncover differences in pace or scope handling.
🔸 2. Releases
The Releases data source allows you to track delivery progress and throughput across one or multiple releases - great for roadmap reviews or stakeholder reporting.
📊 Availability in charts:
Agile Velocity Chart Gadget: Cross-team, Individual (Benchmarking – coming soon)
Agile Cycle Time Chart: Histogram, Trend, Time in Status – coming soon
Agile Burnup Burndown Charts: Burnup, Burndown – coming soon
💡 Tip: Use the breakdown by release option to spot scope changes and delivery dynamics per release.
🔸 3. Issue hierarchies built on the Parent field relationship
Use this data source to track delivery across multi-level structures like Initiatives → Features → Solutions. Set the parent issues and define the depth of the hierarchy (1-3 levels) where the issues contributing to throughput are located:
📊 Availability in charts:
Agile Velocity Chart Gadget: Cross-team, Individual (Benchmarking – coming soon)
Agile Cycle Time Chart: Histogram, Trend, Time in Status
Agile Burnup Burndown Charts: Burnup, Burndown
📌 Use case: Perfect when you need rolled-up insights across nested work items, with full control over what level contributes to progress.
🔸 4. Issue hierarchies built on Issue links and Epics
Use this data source if your hierarchy includes custom issue types above Epics (like Initiatives or Epic Programs) and you want to track their child issues. You can specify the link type and depth of the Epic, so all child issues from connected Epics are included in your velocity calculations:
📊 Availability in charts:
Agile Velocity Chart Gadget: Cross-team, Individual (Benchmarking – coming soon)
Agile Cycle Time Chart: Histogram, Trend, Time in Status
Agile Burnup Burndown Charts: Burnup, Burndown
📌 Use case: Ideal for scaled Agile frameworks where epics are linked upward to bigger strategic items, and you want full team effort reflected under the right parent.
🔸5. Epic static list
Need to monitor key Epics across teams or boards? Just select them manually using the multi‑select list:
📊 Availability in charts:
Agile Velocity Chart Gadget: Cross-team, Individual (Benchmarking – coming soon)
Agile Cycle Time Chart: Histogram, Trend, Time in Status
Agile Burnup Burndown Charts: Burnup, Burndown
💡 Tip: Use breakdown by Epic to understand the dynamics separately.
🔸6. Epic dynamic JQL condition
Use this setup to keep your Epic list dynamic - for example, to track all Epics created during a specific PI. By setting a JQL condition, matching Epics will be added automatically, so your chart stays up to date as new ones appear:
📊 Availability in charts:
Agile Velocity Chart Gadget: Cross-team, Individual (Benchmarking – coming soon)
Agile Cycle Time Chart: Histogram, Trend, Time in Status
Agile Burnup Burndown Charts: Burnup, Burndown
💡Tip: Use breakdown by Epic to analyze each Epic individually.
🔸 7. Saved or custom JQL
Use this when you need full control over what issues get included in your chart. You can also apply extended JQL filters - even ones created using third-party Jira apps like ScriptRunner:
📊 Availability in charts:
Agile Velocity Chart Gadget: Cross-team, Individual (Benchmarking – coming soon)
Agile Cycle Time Chart: Histogram, Trend, Time in Status
Agile Burnup Burndown Charts: Burnup, Burndown, (Sprint Burndown – coming soon)
🔸8. Pre-selected data sources for particular templates
When using a particular template, some data source types might be unavailable during the initial setup. However, once the chart is loaded, you can freely switch to another source if needed:
This flexibility allows you to adapt the chart to your data structure and analysis needs at any stage.
The improved Agile Reports and Gadgets issue type filter lets you precisely control which issue types are included in chart metrics, giving you greater flexibility in reporting.
Once a project is selected, you can fine-tune your selection to include specific issue types like Epics, Stories, or Sub-tasks, depending on your focus:
📊 Availability in charts:
Agile Velocity Chart Gadget: Cross-team, Individual, Benchmarking
Agile Cycle Time Chart: Histogram, Trend, Time in Status - to be updated
Agile Burnup Burndown Charts: Burnup, Burndown, Sprint Burndown – coming soon
Working with releases that share the same name across multiple projects just got easier.
Now, simply pick a project and select one or multiple fixVersions, and see exactly what matters on the chart.
📊 Availability in charts:
Agile Velocity Chart Gadget: Cross-team, Individual, Benchmarking
Agile Cycle Time Chart: Histogram, Trend, Time in Status - coming soon
Agile Burnup Burndown Charts: Burnup, Burndown, Sprint Burndown
The issue list is a handy way to understand the data behind metrics. With this update, you can fully customize the view by adding any columns from your issue layout. More control, more context, right where you need it:
We’ve introduced a refined logic for calculating the Rollover metric based on your feedback. Previously, the work from any past sprint that wasn’t completed was counted as rollover. Now it reflects work that existed in a previous sprint and was carried over into the current one, offering a more accurate view of how work flows between sprints:
At the same time, we’ve slightly revised the legacy logic to keep it available in the issue list. This helps you analyze which issues appeared in multiple sprints, even if they’re not counted as rollover by the updated definition.
The issue list now shows the number of sprints each issue was part of. You can hover to explore sprint history, sort the list to spot anomalies, or apply breakdowns using this data.
We’ve improved how charts interpret multiple “Done” statuses to avoid duplicated counts across sprints.
Previously, if an issue moved to one “Done” status in a sprint and then to another in the next, it was mistakenly counted twice. That made the setup unreliable for tracking real completions.
Now, the chart counts each issue only once - even if it goes through multiple “Done” statuses. As soon as it reaches any of them, it’s considered completed. No double counting, no confusion.
With the Total Work metric, it’s now easier to track how the total scope changes over time, helping teams identify scope changes, avoid unwanted scope creep, and build more realistic forecasts:
By default, the remaining work growth setting is set to 0
, providing a forecast based on the current scope volume. But with this update, you can remove that value to see how the historical scoped change trend affects the delivery date:
This makes your projections feel more real-world, especially in cases where the scope often increases mid-flight. Just make sure to set enough intervals in the past to build the trend line accurately.
We’ve completely reimagined the starting point for working with charts. Instead of listing dozens of individual charts by data source, Agile Reports 8.0 introduces a new Getting started page and a simplified Chart catalog.
Now, when you click the “Create chart” button, you’ll choose from just three chart types (Cycle time chart, Velocity chart, Burnup Burndown chart), and then select your data source in the next step, making the experience more scalable and much easier to navigate:
Agile Reports and Gadgets now give you more flexibility, smarter charting, and better control over data, all with new data sources and deeper metrics. It’s built on Forge, Atlassian’s secure cloud platform, and ready for any Agile setup in Jira, whether you work with Scrum, Kanban, or Scaled Agile.
Agile Reports and Gadgets is a powerful bundle that brings together our core charting apps in one place - for maximum flexibility and deeper insights.
Prefer a more focused setup? Each app is also available separately:
Choose the full bundle - or pick just what you need.
💬 Need help or want to share feedback? Contact support
Vasyl Krokha _Broken Build_
0 comments