nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

✨ Jira dashboards are getting an upgrade - learn more

Allanah Miller

Calling all dashboard enthusiasts!

Over the coming months, we’re upgrading Jira dashboards to give teams a more flexible, visual way to understand work, spot risks, and share progress across Atlassian.

For years, Jira dashboards have helped teams keep an eye on projects, work items, and progress. But as teams rely on more apps to get work done, they need easier ways to bring the right data, context, and insights together in one place.

The new dashboard experience builds on what you already know and love about Jira dashboards, with a modern canvas, richer reporting, dashboard-wide filters, AI-assisted creation, and more ways to bring context from Jira, Jira Service Management, Assets, Goals, DevOps, and more into a single view.

You’ll be able to try the new experience in Jira before any changes are made to your existing dashboards.

⏳ What’s changing for existing Jira dashboards?

We know teams rely on their existing Jira dashboards every day, so we’re taking a gradual approach.

In the coming weeks, teams will be able to create a new or classic Jira dashboard from within the Jira 'Dashboards' landing page.

Your current Jira dashboards will remain available while you try the new experience. You can continue using and creating existing Jira dashboards during the initial rollout.
You’ll get time to explore before migration begins. Migration support and tooling will not begin before 30 Oct 2026. We’ll share in-product updates with the specific timeline before migration options become available for your site.
Migration timing will depend on your dashboard setup. Dashboards that use standard Jira gadgets are expected to be earlier to move. Dashboards that rely on custom gadgets, Marketplace apps, or complex configuration may need more time or guidance.
We’ll provide more detail before any broader migration step. We know admins and teams need clarity on timing, site impact, available choices, and what to expect.

Our goal is to help teams move to a better dashboard experience without losing visibility into the work they already track today.

📊 What can I track with the new dashboards?

With ready-made templates, guided chart building, and richer Atlassian data, you’ll be able to build dashboards around the everyday reporting questions your team cares about most:

Keep goals on track	Quickly understand which work is connected to team or individual goals so you can focus your time on what matters most.
Manage software development	Combine Atlassian work data with DevOps data in a single view, so you always have a pulse on team capacity, deployments, cycle times, and more.
Optimise service health	Get a clearer picture of service desk health by visualising ticket volumes, assignees, response times, and more so you can stay ahead of critical SLA targets.

The new dashboard experience is designed for every team member, giving everyone a flexible way to report on the work that matters most, without needing specialist analytics skills.

🧩 Features we’re excited about

Ready-made templates and flexible layouts

Start with templates for common scenarios like team goals and delivery progress, then arrange, resize, and group charts so your dashboard tells a clear story.

Dashboard-wide filters

Apply filters once to focus multiple charts by team, project, sprint, date range, priority, or work type.

Guided chart creation

Pick the data, chart type, and metric you need through a guided experience. No SQL required.

Connected Atlassian reporting

Bring together data from Jira, Jira Service Management, Assets, Goals, DevOps, and more so teams can understand the complete view of work without switching between tools.

AI-powered assistance

Use Rovo to move from question to dashboard faster, whether you’re asking “How is our sprint tracking?” or “Where are requests getting stuck?”

More context in one place

Add related content like Confluence pages, Loom videos, and supporting links so viewers understand what the numbers mean and what to do next.

🔎 Looking ahead

This is a step toward more connected, AI-assisted reporting across Atlassian.

We’ll continue improving dashboards with more charting options, richer metrics, and deeper connections across Atlassian products. We’ll also share clearer migration guidance as the rollout progresses, including what admins and teams need to know before moving existing dashboards.

We’re excited for you to try the new dashboard experience and build views that help your teams make better decisions, faster.

❓ FAQs

Will my existing dashboards be deleted ?

No. Your current dashboards will remain available while you explore the new experience. We’ll share more detail before any migration steps are introduced.

When will migration begin for my site

Migration will not begin before 30 Oct 2026. We’ll provide in-product updates and additional communication before migration options become available.

What happens to Marketplace app gadgets on my dashboards?

Marketplace app gadgets will not be available in the new experience at launch. We’ll provide more guidance on compatibility and migration tooling as we work with each marketplace app.

Do the new dashboards support all existing Jira gadgets?

The new experience supports common reporting use cases through a modern chart builder. Some legacy or rarely used gadgets may not have a direct equivalent initially.

Can I use the new dashboards with Jira Service Management data?

Yes. The new dashboards bring together data from Jira, Jira Service Management, Assets, Projects, Goals, and DevOps in a single view.

Do I need Rovo to use the new dashboards?

No. AI-assisted creation is optional. You can build dashboards manually using templates and the guided chart builder.

📣 We’d love to hear your feedback

If you run into a bug or have a question, suggestion, or comment, you can select Give feedback when viewing or editing a dashboard to get in touch with us. This will help us shape the feature set and make it even better!

Comments

Sebastian Wigge

Those are great news. We have been waiting for dashboard improvements for a long time. Building, maintaining and using dashboards always felt cluncky with the Jira Standard. With implementation of aggregated data from multiple apps, Dashboard wide filters and new gadgets it looks like you understood the pain points of default dashboards. I'm looking forward to this new experience and hope that the migration of existing dashboards goes smoothly without too much administrative effort.

It would be interesting to know more about the procedure for customers that use apps such as Rich Filters for Jira (Appfire), Custom Charts (Tempo) and others once that's clear. Most importantly: Is the new Dashboard experience compatible with this additional layer or can it even replace the need for those apps?

In any case, a very promising update. Thanks for working on this!

Tomislav Tobijas

Thanks for the update @Allanah Miller ! I've suspected this might be what Atlassian has planned when they introduced Home dashboards.

Just to be clear - the idea is to completely migrate everything from Jira > Dashboards to Atlassian Home > Dashboards, and dashboards within Jira itself will not be available anymore (from a certain point in time)? 👀

Cheers,
Tobi

Allanah Miller

Thanks Sebastian, I appreciate the feedback!

We are working closely with our marketplace partners to ensure their apps will also work on the new dashboards! We will continue to provide updates as the rollout progresses!

Allanah Miller

Thanks Tobi,

The idea is that the new Dashboards come into Jira. So Jira > Dashboards will remain, with the new dashboards available directly there.

The Atlassian Home > Dashboards created during our open beta will be shifted to Jira > Dashboards over time!

Eric M

This would definitely be useful to have.

Monika Rani

This is great news 😀Thank you for the update @Allanah Miller

Mia Tamm _Simpleasyty_

Dashboard-wide filters! 🙌

Also really interested in how the Marketplace gadget migration evolves. There are some very sophisticated dashboards out there, so that transition is probably going to be just as important as the new charting experience itself.

Kate

I'm super excited for this update and have so many users who will be feeling the same!

It would be good to see how this might integrate with the current third party apps (our users are big fans of Tempo's Custom Charts). I would also be keen to see if the functionality provided by Atlassian's

Rich Text Gadget for Jira could be integrated since many of our project teams like to provide additional guidance and notes on the dashboard pages

Rodney Nissen [Work Wranglers] [TJL]

I'm very excited about this change, but as they say, the proof is in the pudding. I'm more than ready to play with it myself!

Vivek Fitkariwala

Hi @Allanah Miller , a question about dashboard filters for widgets built on Jira issue data.

Our widgets fetch issues with JQL and calculate statistics in the app. According to the useWidgetContext docs, native filters reach a widget
as AvpStoredFilter objects (dimensions, comparison, defaultValues).

What we can't find is a supported way to turn those filters into the issues list. Every Jira REST issue query (/search/jql, /jql/match, /search/approximate-count) accepts only JQL, and neither the Dashboard UI bridge nor the REST API accepts a filter expression.

How should a widget apply the active dashboard filters to Jira issue data?

Is there, or will there be, a supported way to get the matching issues or an equivalent JQL (for example a JQL string on each filter, or a filter → JQL helper)?
If apps have to translate filters to JQL themselves, could you document the dimension names and their Jira fields, the comparison operators, the date tokens, and how dynamicDimensionKey maps to customfield_XXXXX?

Michael Bachmann

The current iteration of Home dashboards and all the features and screenshots mentioned in this article seem to be geared solely towards reporting and charts.

Our entire company is HEAVILY reliant on Jira dashboards for their everyday work, especially for those working across multiple Jira spaces.
We use many filter gadgets (filter results, filter counts) with complex JQL queries to filter for the relevant work items for each team, this is currently impossible to recreate using the Home dashboards.

What exactly are these gadgets that "supports common reporting use cases" and which are you declaring "legacy"?

If this new release is just the current Home dashboard functionality, this will be a complete DISASTER for us.

Apryl Harris

@Allanah Miller - It would be optimal to release in Jira sandbox now (if the customer wants to). Is that possible? Early release in sandbox will allow Jira Admin to prepare & understand the new functionality and initial impacts prior to the release to everyone in PROD environments.

Excited to play around with the functionality!

Nestor Rodriguez

I asume that the classic dashboard experience will be able until at least:
- there is a full compatibility between classic dashboards and new dashboards for all gadgets → there are thousands of dashboards in our customer's environment and we can not afford to go to our customer and saying that they'll have to rebuild all of them.
- Jira DC has expired → migrations are a hot topic nowadays and dashboards need to be able to be migrated, otherwise this might be a stopper for our customers for going to the cloud. Moreover, we can not afford add in the scope of all the migrations that we perform the rebuild of the dashboards.

Is this right?

Patricia Francezi_iDev_

@Allanah Miller
I notice that this feature is not available for my JSM standard - the source shows as 🚫 sign. Are you guys sure that this will remove all dashboards from standard?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira-software-cloud

jira-cloud