On 23 September Atlassian told app developers that classic Jira dashboards are being upgraded to a new surface over the coming quarters, that the Forge modules today's gadgets run on are deprecated for removal on 17 May 2027, and that customer rollout has started (developer announcement, 23 September; Jira Cloud platform changelog). That post was written for the people who build gadgets. This one is for the people whose users will ask "where did my dashboard go."
What is actually changing
The new dashboards are the ones that launched as Home Dashboards; they are moving into Jira and replacing the classic dashboard page. They bring flexible layouts, interactive widgets, native Bitbucket widgets, and an AI insights layer that is still in early access. They do not carry Confluence data yet, and Marketplace widgets cannot read dashboard filters yet; Atlassian says a filters capability for Forge is weeks away.
Your site will get dual-create first: users can build a classic dashboard or a new one, side by side. Existing dashboards keep working through that phase.
The sentence every admin should read twice
From Atlassian's own post: once a tenant that does not use any Marketplace dashboard apps is migrated to the new platform, access to legacy dashboards is switched off. Tenants that do depend on Marketplace gadgets are held back in separate cohorts until the app vendors have shipped upgraded widgets.
So the thing that decides when your site loses classic dashboards is not a date on a calendar. It is whether any dashboard on your site uses a third-party gadget. That is the list to build this week.
How to build the list
Jira has no report that says "these dashboards use app gadgets." Two routes:
- The REST route. List dashboards gives you every dashboard on the site (page through it), and get gadgets lists each dashboard's gadgets with their module keys. Native gadgets carry Atlassian keys; Marketplace gadgets carry the app's key. Export to a sheet: dashboard, owner, shared with, gadget key, app. Run it as a site admin so private dashboards are included.
- The people route. Ask the owners of your top twenty shared dashboards (by how many groups they are shared with) which gadgets they cannot live without. The REST list tells you what exists; the owners tell you what matters.
What you get is three groups: dashboards with no app gadgets (these migrate first and lose classic access at that point), dashboards with app gadgets from vendors who have already announced an upgraded widget, and dashboards with app gadgets from vendors who have not. The third group is the one to raise with the vendor now; 17 May 2027 is their deadline, not yours, but your users are the ones stranded if they miss it.
What does not migrate by itself
Atlassian says the configuration inside Marketplace gadgets (saved filters, project selections, colours) will need an explicit migration path written by each vendor; Atlassian will provide tooling, but the vendor has to use it. Native gadget properties are preserved. So a dashboard built entirely on native gadgets should come across intact; a dashboard built on an app's gadget comes across as well as that vendor's migration function is written.
Two earlier stories that this one absorbs
In 2025 Atlassian announced, then paused, the removal of five native gadgets (Road Map, Bubble Chart, Heat Map, Projects, Labels). That pause was explicitly "while we build new cross-product dashboard experiences." This is those experiences. If your teams still lean on any of those five, treat them as gadgets with no upgraded replacement announced, and find out what the new surface offers before the switch reaches you.
And Connect apps are on their own end-of-life path. A dashboard gadget from a Connect app has two migrations ahead of it, Connect to Forge and gadget to widget. Vendors who have not started the first are unlikely to be early on the second.
What to tell your users, in one paragraph
"Jira dashboards are getting a new version. For a while you will be able to create both kinds. Your existing dashboards keep working during that period. If a dashboard of yours uses a gadget from an add-on, tell us which one, because that decides when your site moves." Send it before the dual-create option appears, not after the first support ticket.
The dates
- 23 September 2026: rollout begins, dual-create first, all tenants over the coming weeks.
- Now: developers can opt a site in early through the Developer Canary program; useful for a sandbox, not for production.
- 17 May 2027: legacy gadget modules removed; any Marketplace gadget not migrated stops rendering.
Checklist
- Export every dashboard and its gadget keys this week; keep the sheet.
- Split it into native-only, vendor-ready, vendor-not-ready.
- Email the not-ready vendors with the dashboard count you depend on.
- Turn on the new dashboards in your sandbox and rebuild one important dashboard by hand to learn what changed.
- Draft the user note now.
- Before any dashboard moves, capture a baseline of the ones people depend on: a screenshot plus each gadget's filter, JQL and colour settings, so you can verify behaviour after migration, not just presence (credits to: @Mia Tamm _Simpleasyty_).
Verified against the Atlassian developer-community announcement and the Jira Cloud platform changelog on 27 September 2026
Updated 29 September 2026: checklist item 6 added
