Changelog

The requestRemote bridge API allows Forge apps to integrate directly with remote backends from the UI Kit and Custom UI applications via the Forge bridge.

This API is similar to invokeRemote, where requests include a Forge Invocation Token (FIT) as a bearer token in the authorization header; however, the request is not an official invocation that passes through the Forge platform. Therefore, requestRemote will not include OAuth tokens, even if configured for the remote, and will not be reflected in invocation metrics in the Developer Console.

For more details, see requestRemote.

The new Rolling releases feature is now available through Forge’s Early Access Program. To join the EAP, please complete this sign-up form.

Rolling releases let you decouple app permissions from app code, allowing code updates to be deployed independently of permission changes. This means your app can be upgraded to a new code version even if admins haven't approved new permissions yet, addressing the version fragmentation problem .

With rolling releases, developers can ship code improvements and bug fixes more frequently without being blocked by permission approval processes, while customers benefit from staying on current, secure versions. Admins maintain control by approving permission changes separately from code updates.

For more information on this feature, refer to the RFC-106: Future of Forge versioning - Permissions post.

The Jira full page module enables developers to build fully custom, chromeless app experiences within Jira Cloud, hosted directly on Forge.

This preview is accessible via the following URL: https://<tenant-name>/forge-apps/a/<app-id>/e/<environment-id>/r/<route-prefix>/<app-route>

For more information, see the Jira full page (Preview)

We are deprecating the forge webtrigger command as a leaf command in favour of 3 new sub-commands for managing webtriggers.

• forge webtrigger create for creating a webtrigger URL

• forge webtrigger list for listing existing webtrigger URLs

• forge webtrigger delete for deleting a webtrigger URL

The forge webtrigger and forge webtrigger create command will function exactly the same until such time as the forge webtrigger command is no longer supported in May 2026, in line with our deprecation policy.

You can now configure the Forge Content Byline Item module to open in a modal instead of a pop-up. The modal supports both standard and full-screen sizes, giving you more flexibility in how your content is displayed. This can be done by using viewportContainer: modal in your manifest.

bitbucket:projectSettingsMenuPage module is now available. You can use this module to build a custom project settings page. See the project settings menu page for details.

bitbucket:repoCodeFileViewer module is now available. You can use this module to build a custom file viewer. See the file viewer page for details.

We've introduced the bitbucket:workspaceGlobalPage module for Forge apps. Your app will now appear as a menu item in the Apps section of the Bitbucket workspace navigation, displaying your custom page content when users select it.

To use this module, update your app’s manifest to include bitbucket:workspaceGlobalPage.
For implementation details and examples, see the bitbucket:workspaceGlobalPage module reference.

We are re-enabling automatic Connect to Forge migrations, following the temporary pause which started on Sep 23, 2025

Apps which were impacted by or published to the marketplace following this pause will now see Connect installations progressively move to Forge as long as they meet the minor update criteria. The pace of the migration will be dynamically adjusted to ensure high throughput and reliability of the pipeline as we clear these pending updates.

The new Forge rovo.open method is now available through Forge’s Early Access Program. To join the EAP, please complete this sign-up form.

The rovo.open method allows you to open the Rovo chat sidebar and create a new conversation with either a default or specified Rovo agent.

For more information, see the Rovo documentation.

Forge LLM is now available through Forge’s Early Access Program. This feature allows Forge apps to integrate with an Atlassian-hosted large language model (LLM) capability, meaning that apps that use the feature will still be eligible for the Runs on Atlassian program.

At launch, only the Claude model family is supported. Support for additional model families will be added soon.

Forge platform will be undergoing maintenance in commercial production on November 23, 2025 for approximately 1 minute between 5:30-6:30am UTC

During this interval, below capabilities will not be available intermittently:

• Create/update/delete apps

• Deploy apps

• Install/uninstall/upgrade apps

App invocations will continue to work for existing users of the apps. However, new customers might not be able to use apps as consent process will be impacted during this interval as well.

We’re updating Forge’s invocation rate limits to improve our long-term scalability and flexibility. This change will help ensure our platform can adapt and respond to unpredictable high bursts of traffic.

Currently, we limit the number of invocations to 1,200 per one-minute fixed window.

We are changing this limit to a per one-second sliding window instead, scaling the limit appropriately. In addition, invocations from Forge events and user-triggered interactions will have different limits.

The sidebar will now span the full height of your Atlassian app, making it easier to find and interact with. Starting late November 2025, this update will roll out to all customers who haven’t customized the look and feel of their sites. This change won’t affect the width and height of your Forge and Connect apps.

Along with this, we’re introducing a few improvements to sidebar interactions:

• Double-click to collapse: When expanded, double-click the button to quickly collapse the sidebar.

• Global shortcut: Use Ctrl + [ to expand or collapse the sidebar at any time.

• Helpful tooltips: Tooltips will appear to guide you through the interaction.

For sites with customized look and feel, the full-height sidebar can disrupt intentional design choices, such as:

• Custom logos and titles

• Favicons

• Navigation colors

• Dark and light mode settings

Because of this, the sites with customized look and feel won’t receive the update just yet.

For the sites without customized look and feel, we’re opening up the opportunity on Nov 21, 2025 to let you use this feature early and test it with your apps. If you’re interested, please sign up here with your site details.

As announced previously, the ability to use triggers as a dynamic module is now available under Forge’s Early Access Program (EAP).

To start testing, sign up for the EAP here.