# Jira dashboards are being replaced: what is confirmed and what to do now

> Jira dashboards are being replaced: migration no earlier than 30 Oct 2026, legacy gadget modules removed 17 May 2027. What is confirmed and what to do now.

Source: https://www.xalt.de/en/blog/jira-dashboards-new-experience-migration/

Martin Runge Head of Atlassian at XALT · 29 September 2026 · 7 min

Your Jira dashboards are being replaced, and the rollout has already reached your site. On 23 September 2026 Atlassian announced that classic dashboards and gadgets are giving way to a new, chart based experience built on Forge. As of 28 September it is on 100 percent of Cloud sites. If you open Jira today, you can already create a new style dashboard next to your classic ones.

Most admins we have spoken to this week had no idea. There is a reason for that: the announcement went out through two channels on the same day, a notice in the Developer Community for app vendors and a post in the Atlassian Community for customers. The developer notice is the one that circulated. The customer post was largely missed, including by experienced administrators.

Dashboards are the most visible reporting surface in Jira. Project managers and service owners work in them every day. The first signal most sites will get is an in product notice roughly two weeks before migration. If your users learn about the change from a banner before they hear it from you, you have lost control of the story. That makes it worth separating things clearly right now: what is confirmed, what has only been said, and what is still open?

## The dates you need to know

| Date | What happens |
| --- | --- |
| 23 September 2026 | Atlassian announces general availability of the new Forge dashboard widget modules. The customer post is published the same day. |
| 28 September 2026 | The new dashboard experience reaches 100 percent of sites. Classic and new dashboards can be created side by side. |
| No earlier than 30 October 2026 | Migration of existing dashboards may begin. Not before. |
| 17 May 2027 | The legacy gadget modules for Marketplace apps are removed. Any app gadget its vendor has not rebuilt by then stops working. |

As of 29 September 2026, based on the two Atlassian sources listed at the end of this post.

Two dates belong in every conversation about Jira reporting: **no earlier than 30 October 2026** for the start of migration, and **17 May 2027** as the fixed end date for the legacy gadget modules.

## What changes on your dashboards

The new model works fundamentally differently from the gadgets you know:

- **Metric based charts instead of gadgets on filters.** Charts are built in a guided chart builder rather than by pointing a gadget at a saved filter.
- **Dashboard wide filters** that apply to several charts at once, instead of configuration per gadget.
- **AI assistance through Rovo** when creating dashboards.
- **Data from several sources:** Jira, Jira Service Management, Assets, Goals and DevOps sources in one place. Bitbucket widgets are available natively. Confluence data is not supported yet.
- **Templates, flexible layouts and embedded content** such as Confluence pages, Loom videos and links.

You will find the new dashboards at Jira \> Dashboards. The developer docs initially read as if the new widgets lived only in Atlassian Home. Atlassian has since clarified that Atlassian Home dashboards will move to Jira \> Dashboards over time.

## How the rollout works

Migration happens in three phases:

- **Side by side (dual create).** You can create classic and new dashboards. Every site has been in this state since 28 September 2026.
- **Cohort based migration.** Sites with no dependency on a Marketplace dashboard app migrate first. After that, access to classic dashboards is switched off for those sites.
- **Cohorts timed to vendor readiness.** Sites that depend on Marketplace dashboard apps migrate later, timed to when each vendor is ready. Atlassian has stated it will not strand customers who depend on Marketplace apps.

**The part almost nobody has noticed**

Read that again: right now a dependency on a Marketplace dashboard app buys you more time, not less. Sites running only standard gadgets go first. If your reporting sits on Custom Charts or eazyBI, for example, you are in a later wave. That does not move 17 May 2027, though.

## What this means for Marketplace apps

- Marketplace app gadgets are **not available** at the launch of the new dashboards.
- Vendors have to rebuild their gadgets from the legacy jira:dashboardGadget module to the new dashboards:widget module. Atlassian supports this with code mods and a platform assisted migration.
- **Gadget configuration does not migrate automatically.** Each vendor has to decide which stored settings need an explicit migration path.
- Display conditions are not supported on the new widget module and are not on Atlassian's roadmap.

For you, this means: whether your app based reports survive the switch depends on the vendor's timeline. Get it in writing.

## Stated, but not yet documented

In forum replies and partner conversations, Atlassian has mentioned further points. They sound good and are most likely meant that way. They are not in the official documentation yet:

- Existing dashboards are expected to get migration tooling. Rebuilding from scratch is not the intended path.
- Filter Results, Two Dimensional Filter Statistics and Created vs Resolved are expected to have equivalents that migrate automatically.
- Dashboard permissions and smart link embeds are planned to carry over.
- Before a site migrates, there should be at least two weeks of in product notice, followed by a 30 day grace period in which you can switch between the old and the new experience.
- Saved filters and JQL are said to remain important. JQL filtering for charts is being worked on.
- Some legacy or rarely used gadgets may have no direct equivalent at first.

**Not a commitment yet**

This is good news, and it is probably true. Plan with it as direction, but do not base a firm commitment to your team or business units on it. It goes into a commitment when Atlassian documents it, not before.

## The open question that matters most

Charts are metric based today. JQL filtering, which would let you scope a chart to a saved filter, is still in progress. If it does not land before 30 October 2026, a migrated chart cannot reproduce most filter driven gadgets. That single answer decides how calm this migration will feel for you.

Other points are still open as well: Do migrated charts return the same numbers as the gadgets they replace? What exactly carries over for permissions and sharing, for example on dashboards shared with a group? And which standard gadgets have no equivalent? There is no reliable list for that yet.

## What you should do now

Two steps, in this order: try it yourself first, then tell people. Do not send notes about an experience you have not opened yourself.

### This week and next: get hands on

1. **Try the new chart builder.** Create a new style dashboard on a test site and rebuild one you know well. The goal is not a polished result. The goal is to find out where the metric based model cannot reproduce a filter driven gadget. That gap is the real conversation with your business units.
2. **Take inventory.** Which dashboards are actually opened? Which gadgets sit on them, which of those come from Marketplace apps, and which saved filters feed them? Without that list, any recommendation is a guess.
3. **Get vendor timelines.** Flag every gadget that comes from a Marketplace app and ask the vendor for their migration date to dashboards:widget and whether configuration migrates too. In writing.

### After that: tell your users

A short, factual note to everyone who works with Jira dashboards. Not an alarm, and no commitments beyond what is documented. It should cover:

- the two dates: no earlier than 30 October 2026 and 17 May 2027
- what keeps working in the meantime: classic dashboards stay available until your site migrates
- an offer to look at the most important dashboards together

### Starting now: define KPIs independently of the tool

"Open tickets per team per week, from this filter, target under X" survives a change of reporting layer. "The Two Dimensional Filter Statistics gadget configured like this" does not. This applies to every requirement and specification you write from now on.

## Conclusion

The switch to the new Jira dashboards has been decided and is already underway. No reason to panic, but a good reason to take inventory and define your KPIs cleanly now. If you know what sits on your dashboards and where the data comes from, you can approach the migration calmly. Everyone else will find out from a banner.

## Sources

- [Atlassian Developer Community: Jira Dashboards upcoming changes and new Forge dashboard widget module general availability](https://community.developer.atlassian.com/t/jira-dashboards-upcoming-changes-and-new-forge-dashboard-widget-module-general-availability/102826)
- [Atlassian Community: Jira dashboards are getting an upgrade, learn more](https://community.atlassian.com/forums/discussion/3287564/jira-dashboards-are-getting-an-upgrade-learn-more)

## Dashboard inventory with XALT

Together we look at which dashboards are actually used, which gadgets come from Marketplace apps and how your KPIs survive the switch.

[Explore Atlassian Services →](https://www.xalt.de/en/atlassian-services/)

## More articles

### [Why Agentic AI Becomes the Standard in 2026](https://www.xalt.de/en/blog/why-agentic-ai-becomes-the-standard-in-2026/)

Agentic AI systems are replacing the chatbot era. No more hype – real automation that takes over workflows instead of just responding to them.

*News*

### [XALT Named Finalist for Atlassian Partner of the Year 2026 – Government EMEA: What It Means for the Public Sector in DACH](https://www.xalt.de/en/blog/xalt-finalist-atlassian-partner-of-the-year-2026/)

Atlassian has named XALT a finalist for "Government Partner of the Year – EMEA." What that means for our public-sector approach, and why Atlassian cloud migration is now a priority for government agencies.

*News*

### [Insights from the Enterprise AI Summit 2026: How Leading Companies Turn AI into Real Business Outcomes](https://www.xalt.de/en/blog/insights-enterprise-ai-summit-2026/)

From the Enterprise AI Summit 2026 in San Jose: the 5 key takeaways for IT leaders, plus real business outcomes from Cisco, John Deere, LaunchDarkly, Skypoint Health, Disney, and Vanguard.

*News*

---

*This version is for AI agents. Every page of this site is available as Markdown: append `index.md` to its path. Index of all pages: [llms.txt](https://www.xalt.de/llms.txt)*