[changelog] New Forge dashboard modules now generally available #37

Changelog entry: CHANGE-3453
Published: Tue, 22 Sep 2026 05:04:42 GMT
Category: Announcement

What is changing

The new Forge dashboard modules are now generally available (GA). They target the upgraded Jira dashboard experience, which begins rolling out to customers on September 23rd, 2026 and coexists with classic Jira dashboards during the rollout:

• dashboards:widget: creates custom content blocks (widgets) on the new dashboard surface.
• dashboards:backgroundScript: runs background logic for dashboard extensions.

Atlassian says apps using the legacy jira:dashboardGadget and jira:dashboardBackgroundScript modules should begin planning migration to the new modules. There is a new dashboards:widget manifest reference with configuration details and schema.

Likely impact on forge-sim parity

• Modules / manifest: two new module keys (dashboards:widget, dashboards:backgroundScript) need to be recognized by the manifest loader and module registry. Today an unknown module key is likely rejected or ignored; per the core parity rule, a manifest Forge accepts should deploy in forge-sim.
• Renderer / UI module detection: dashboards:widget is a UI module (resource + render) and should flow through the same UI Kit / Custom UI rendering path as jira:dashboardGadget, including any widget-specific context shape (dashboard id, widget id, config/edit mode). Check the manifest reference for new properties before assuming gadget-equivalence.
• Background scripts: dashboards:backgroundScript is presumably a headless resource that runs alongside widgets (like jira:dashboardBackgroundScript); confirm whether it has a resolver/bridge surface that needs simulating.
• Fixtures / docs: the capability matrix and any dashboard test apps should list the new modules; legacy gadget modules remain valid for now, so no removal.

Link: https://developer.atlassian.com/platform/forge/changelog/#CHANGE-3453