Atlassian removes legacy Jira Forge dashboard modules on 17 May 2027: app makers must migrate to the new dashboards modules

Atlassian removes legacy Jira Forge dashboard modules on 17 May 2027: app makers must migrate to the new dashboards modules

30 September 2026: Atlassian has deprecated two Forge modules that apps use to put gadgets on Jira dashboards, and will remove them on 17 May 2027, according to its Jira Cloud platform developer changelog. Apps must move to new modules built for the upgraded Jira dashboard experience.

Not yet independently verified. This rests on Atlassian's own developer changelog; the exact publication date of the deprecation entry was not confirmed (it appears between entries dated 22 September and 5 October 2026). No independent report was found. We will update this when it can be confirmed, and remove this note.

What is changing

The changelog says these Forge modules are deprecated:

• jira:dashboardGadget
• jira:dashboardBackgroundScript

They are replaced by dashboards:widget and dashboards:backgroundScript, which Atlassian announced as generally available on 22 September 2026. Atlassian says that for apps to keep working on the new Jira dashboard experience, developers must update their app manifests to the new modules and complete the migration before 17 May 2027 to avoid disruption for users. During the roll-out, the new dashboard experience coexists with classic Jira dashboards.

Who is affected

Developers of Atlassian Marketplace apps and in-house Forge apps that add gadgets to Jira dashboards, such as reporting, time-tracking, project-health and analytics tools. Jira customers are affected indirectly: a dashboard gadget from an app that has not migrated may stop working after the removal date.

What to do

1. App developers: check your manifests for the two deprecated modules and plan the migration, including testing on both classic and new dashboards.
2. Jira administrators: list the Marketplace and custom apps that provide dashboard gadgets your teams rely on.
3. Ask each vendor when it will ship a version using the new modules.
4. For in-house apps, put the migration on your roadmap well before May 2027.

Why it matters for buyers

Platform changes like this are a hidden cost of relying on third-party apps inside SaaS tools. A long notice period helps, but dashboards often carry reporting that executives depend on. Treat the date as a vendor-management task, not just a developer one.

Related on TrustList:

• Atlassian fixes critical file-read flaw in its Data Center products

Sources

• Atlassian Developer: Jira Cloud platform changelog - 5 October 2026