This changelog is the source of truth for all changes to the Forge platform that affect people developing Forge apps.
See what's next for Forge on our platform roadmap.
Some functionality in Forge remains in Early Access Program (EAP) while we're still making changes that may break your apps. Learn more about the current functionality in EAP.
Forge is enabling user-token support for unlicensed users in Forge function and Forge Remote invocations.
Apps can make online and offline calls on behalf of eligible unlicensed users, including calls from Forge resolvers and Forge Remote. Online calls use the invoking user’s context, while offline calls can act on behalf of a specified user where supported.
Existing Forge app permissions, product permissions, and API-specific access controls continue to apply. This change does not enable anonymous-user access.
This includes support for eligible unlicensed users accessing apps through the Jira Service Management portal.
The Forge global:ui module has moved from the Early Access Program (EAP) to Preview. You can now build apps that look and feel like Atlassian core products, featuring configurable side navigation and a dedicated entry in the Atlassian app switcher.
What’s changing
Increased sidebar customization: New components are available for the sidebar, including MenuSection, MenuSpacer, ReorderableMenuItems, SidebarFooter, and SearchableFlyoutMenuItem. You can also use UI Kit and custom icons.
Relevant search results: The Rovo search bar now prioritizes results from Teamwork Graph objects associated with the global:ui app you are viewing.
Custom search results pages: Pressing Enter in the search bar now navigates to your app’s /search?text=<input> route, allowing you to build a custom search results experience.
Compatible with all installation models: The global:ui module is now compatible with site, cross-context, and unit-level installations.
What you need to do
Review the global:ui documentation to understand the module's capabilities.
Explore the component reference for details on the new sidebar components.
Learn more about ingesting Teamwork Graph objects to improve search relevance for your app.
A new RFC is ready for review at https://community.developer.atlassian.com/t/rfc-154-ui-modifications-for-forge-custom-fields-in-jira-and-jsm/103577
The byline on Confluence Cloud pages, live docs, and blog posts will show a single row of apps by default. Users can click to expand the byline and see any additional rows of apps.
We’re making this change to improve the customer experience by reducing Cumulative Layout Shift (CLS) in Confluence pages. This prevents page content from moving as apps load, providing a more stable reading experience for users.
Site admins who want to show all byline apps by default can enable Show all byline apps by default under Confluence administration → General configuration.
No app changes are required. All byline apps remain available. Depending on your app’s position, the number of installed apps, and the available screen space, users may need to expand the byline to see your app.
What's changing
We're introducing a new sharing level for Forge and OAuth 2.0 (3LO) apps: organization-level sharing. With it, you can share your app with anyone in the same Atlassian organization as the app owner.
Key details:
Restricted installation: Only members of the app owner's organization can install the app using the installation link.
Existing installations: If you change a publicly shared Forge app to organization-level sharing, existing installations on sites outside your organization will keep working.
Upgrade restrictions: For apps updated to organization-level sharing, future app upgrades will only be available to members of the app owner's organization. Installations outside the organization stay on the current version unless upgraded by the app developer.
What you need to do
To use this new sharing level:
Navigate to the Developer Console and select your app.
Select Distribution from the left menu.
Under Distribution controls, select Edit.
Choose the Sharing within organization option and save your changes.
For more information on app distribution, see the distribute your apps documentation.
What's changing
We've updated the minimum compatible Node.js version for the Forge CLI. The CLI now requires Node.js 22.23.4, 24.22.1, 26.12.1, or newer.
Node.js 20 has reached end of life and is no longer supported. To continue using the Forge CLI to develop and deploy your apps, you must upgrade your local development environment to one of the supported versions listed above.
What you need to do
Check your current Node.js version by running node -v in your terminal.
If you are running a version older than the requirements, download and install a supported version from the Node.js website.
Update your Forge CLI to the latest version by running:npm install -g @forge/cli@latest
Verify the installation by running forge --version.
For more information on setting up your development environment, see the Getting started guide.
A new RFC is ready for review at https://community.developer.atlassian.com/t/rfc-152-increasing-maximum-memory-for-forge-functions/103441
As previously announced, the jira:fullPage and confluence:fullPage modules have been removed on 30 September 2026 in favor of the unified global:fullPage module.
What’s changing
The product-specific jira:fullPage and confluence:fullPage modules are no longer supported in the Forge manifest.
Requests routed to legacy URLs will automatically forward to the corresponding global:fullPage URL.
Users accessing legacy paths will see a prompt to update their bookmarks.
Automatic forwarding support will be maintained until December 18, 2026.
If you haven’t already migrated your apps, refer to global:fullPage documentation to get started: https://developer.atlassian.com/platform/forge/manifest-reference/modules/global-full-page/
What's changing
From January 1, 2027, Atlassian cloud will add new IP address ranges as we expand our cloud infrastructure.
The new ranges are in addition to our existing ones.
The new ranges are:
New range: 131.162.88.0/21
Requests to Atlassian (browsers and your clients calling Atlassian APIs): 131.162.88.0/23
Requests from Atlassian (webhooks, Connect lifecycle calls, and other requests from Atlassian to your app): 131.162.90.0/23
What you need to do
If your app, remote backend, or integration allowlists Atlassian IP addresses, you must add these ranges before January 1, 2027, to avoid service interruptions.
These ranges are already included in our official IP range list (viewer tool). If you automate your allowlist updates from this file, no further action is required. For more details, see our documentation on IP addresses and domains for Atlassian cloud apps.
EARLY ACCESS: Forge Global Apps
We are ready to kick off the Forge Global Apps Early Access Program (EAP). Forge Global Apps are installed in the platform and can optionally link to one or more Atlassian apps.
What's changing
Installation into unit instead of an Atlassian app workspace
Apps can work across sites in a unit
No required Atlassian app link
What you need to do
Sign up for the EAP: submit a request https://ecosystem.atlassian.net/servicedesk/customer/portal/1040/create/18611 and we will get in touch with instructions soon
The Teamwork Graph Consumption API is now moving into Preview, providing relationship-first querying across Atlassian Cloud objects and connected third-party tools.
What's changing
The Teamwork Graph API lets you query connected context across Jira work items, Confluence content, Loom videos and meetings, external development artifacts, Goals, and Teams using a unified GraphQL endpoint.
Key capabilities in this release include
Curated queries: Supported, typed GraphQL fields for common traversals (such as atlassianUserAssignedJiraWorkItems or confluencePageContributors) with built-in Relay cursor pagination (first, after). No query registration is required.
Persisted Cypher queries: Custom graph traversals registered ahead of time to receive a persistent query key (queryKey), which you execute at runtime via the customQuery GraphQL root field.
Granular object-level scopes: Permissions now use fine-grained scopes following the read:graph:<object>:<product> pattern (such as read:graph:issue:jira and read:graph:page:confluence), giving site administrators precise control in Connected Apps.
What you need to do
Update your Forge app manifest.yml permissions to request the specific read:graph:<object>:<product> scopes required for your queries.
If your app currently uses ad-hoc runtime Cypher queries, migrate to typed fields in the curated queries documentation or register custom queries using the persisted Cypher queries guide.
Dynamic modules, customer-managed egress, and customer-managed remotes are now generally available on the Forge platform.
Dynamic modules let a Forge app register and manage modules at runtime through the Dynamic Modules API, rather than declaring them statically in the manifest. These modules are available across Jira, Confluence, and Jira Service Management.
Customer-managed egress lets Atlassian administrators configure the external domains a Forge app may send data to.
Customer-managed remotes let Atlassian administrators configure the remote backends a Forge app may communicate with.
For more information, see Dynamic modules and Customer-managed egress and remotes.
These capabilities are not currently supported for Atlassian Government Cloud.
These capabilities follow their earlier Preview releases: Forge Dynamic Modules Preview and Customer-managed egress and remotes Preview.
What's changing
Forge display conditions for Jira and Jira Service Management (JSM) modules now support arrays under the and, or, and not logical operators.
Previously, manifest keys had to be unique at each level, which made it difficult to repeat the same condition type or group multiple logical expressions. With this update, you can use an array of condition objects to define complex visibility logic more easily.
For example, you can now structure your manifest to group conditions or repeat the same condition type:
1
2
3
4
5
6
7
8
displayConditions:
or:
- and:
- entityPropertyExists: { entity: user, propertyKey: a }
- entityPropertyExists: { entity: user, propertyKey: b }
- and:
- entityPropertyExists: { entity: user, propertyKey: c }
- entityPropertyExists: { entity: user, propertyKey: d }
What you need to do
No action is required for existing apps, as the previous syntax remains supported. If you want to simplify complex logic or repeat conditions in your Jira or JSM modules, you can update your manifest to use the new array-based syntax.
For more details and examples, see the Forge display conditions documentation.
The visual refresh of the labelling system (which consists of our tag, lozenge, and badge components) is now available by default, both when using the components directly and in Forge UI Kit. The feature flag that previously controlled access to the refreshed look has been removed, so you no longer need to enable it to use the new appearance.
This follows our earlier announcement of the labelling system changes, when the refreshed look was available behind a feature flag.
Date label and Date dropdown trigger are also now generally available (GA). These new additions to the labelling system were introduced without a feature flag.
Rate this page: