Deprecation of confluence:fullPage and jira:fullPage modules
- Announced
- Effective
- Sunset
- APIs
- forge-core-platform
- Severity
- breaking, set by
reef/atlassian-rule-v1 - Source
- https://developer.atlassian.com/changelog/#CHANGE-3380
We are deprecating the confluence:fullPage(Preview) and jira:fullPage(Preview) modules on 2026-09-30. These modules are being replaced by the new global:fullPage(Preview) module, which provides a unified way to create immersive, full-screen experiences for your Forge apps across Atlassian products.
The global:fullPage module is based on the same underlying infrastructure as the product-specific modules, so you can expect a consistent experience with minimal migration effort.
What you need to do To ensure your apps continue to function correctly, you must migrate to the global:fullPage module before the deprecation date.
- Update your app manifest to use the
global:fullPagemodule. - Define the
compatibilityproperty in your manifest to specify which Atlassian products your app requires. - Update any internal routing or links to use the new URL format:
https://<site-hostname>/apps/full-page/<installation-id>/<route-prefix>/<app-route>.
For detailed migration steps and configuration options, refer to the global:fullPage documentation.
The text above is Atlassian's. reef added the severity, the dates it could read from the text, and the endpoints and scopes named in code.