Changelog

On Dec 26, 2025, we announced a temporary delay to billing for asynchronous Forge app invocations to help you plan and prepare for its upcoming costs. This billing will now commence on Jul 1, 2026.

A Forge app invocation is classified as asynchronous when invoked from the following Forge modules:

• Scheduled triggers

• Async Events API

• Trigger

Usage and cost visibility for asynchronous invocations is now available in the Developer Console. This usage is reported separately from synchronous invocations.

We added a new Installations Permissions page in the developer console that provides a better way to track permissions for each installation used by your app. This page features the following:

• Version & permission details: view each individual installation’s exact permissions and version.

• Scope & egress tracking: this dashboard now features a permission overview for Scopes and Egress, listing each item alongside its current status.

Whenever applicable, the app.license field in the Forge Invocation Token (FIT) received at the Forge Remote during requestRemote calls now contains a real marketplace license (alongside other license fields). Previously, this field could only provide license overrides.

Following the Preview release, the Forge bridge rovo API is now generally available.

The Forge bridge rovo API contains the rovo.open() method, which allows you to open the Rovo chat panel and prompt a new conversation with either a default or specified Rovo agent.

To use this, run npm install @forge/bridge@latest on the command line to install the latest version of @forge/bridge.

For more information, see the documentation.

The Forge platform will be undergoing maintenance in FedRAMP production on March 29, 2026 between 11am - 12am UTC.

There should be a few minutes of downtime within this window. During this time, the following capabilities will not be intermittently available:

• Creating, updating, or deleting apps

• Deploying apps

• Installing, uninstalling, upgrading apps

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

Between Mar 19, 2026 and Apr 10, 2026, all updates to Forge apps with over 50,000 users will be classified as major version updates. You can use the forge version bulk-upgrade command to roll out updates to customer sites during this period.

This temporary change will allow partners to manage the migration of customers in a predictable manner. Downstream services can then absorb the increased traffic without unpredictable spikes.

For detailed information on how to use forge version bulk-upgrade, see https://developer.atlassian.com/platform/forge/cli-reference/version-bulk-upgrade/.

This change will not affect how apps qualify for the Forge revenue share rate. Your latest deployed app version determines revenue share eligibility. Customer roll-out status is not assessed in the eligibility criteria.

A cost dashboard is now available at the developer space level in the developer console, providing a clear, consolidated view of estimated monthly costs for all apps used within that space, calculated from their incurred monthly usage. This dashboard highlights top cost drivers and supports filtering and drill-down, enabling teams to quickly understand where spend is concentrated, investigate anomalies, and make more informed decisions about app usage and optimisation.

We've improved how errors from https://developer.atlassian.com/platform/forge/manifest-reference/modules/jql-function/ are surfaced to end users in Jira. This functionality will be rolled out for all customers in next 2 weeks.

Previously, when a custom JQL function returned an error, Jira treated it as a generic server error and End users would see a non-descriptive message — "We couldn't load your search results".

Now, errors returned by custom JQL functions are classified as JQL validation errors and displayed inline, just like native JQL errors. If your app returns a custom error message, that message is shown directly to the end user.

The jira:globalBackgroundScript module is now more powerful and adds following major functionality to the module -

• Experience-based access control - Restrict which Jira views your script runs on using the experience property in the manifest. If no experience is specified, the script will not run anywhere.

• Modal support - Open modal dialogs from a background script on any allowed view using the https://developer.atlassian.com/platform/forge/apis-reference/ui-api-bridge/modal/.

• View context access - Access view-specific context such as issueKey, projectId, boardId, and project.type depending on the current Jira view.

Please read more here https://developer.atlassian.com/platform/forge/manifest-reference/modules/jira-global-background-script/.

We are pleased to announce the availability of multi-user app ownership for OAuth 2.0 (3LO) apps in the developer console.

• Multiple admins - You can assign multiple admins to your OAuth 2.0 apps in the developer console.

• Ownership transfer - The OAuth 2.0 app ownership transfer option is now available in the developer console.

The forge uninstall command now features a --batch option, allowing you to uninstall up to 10 installations at once. This option supports filtering for specific products and environments (namely, through the -p / --product and -e / --environment options). However, you can only use --batch to uninstall apps on non-production environments.

We've introduced a new asynchronous bulk API that allows Jira administrators to pin or unpin Forge app issue panels to multiple projects in a single request — processing up to 1,000 projects at once.

For app developers: Integrate this API into your Forge app to give Jira admins a centralized view for managing issue panel visibility across projects. For full API details, see: https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-panels/#api-rest-api-3-forge-panel-action-bulk-async-post

Forge embedded macros are now available in Preview.

Forge apps can now render embedded Forge bodied macros through the AdfRenderer component (UI Kit) and the view.createAdfRendererIframeProps method from @forge/bridge (Custom UI).

Update to the latest version of @forge/bridge with npm install @forge/bridge@latest

For more information, see documentation.

Following the EAP release, Custom Metrics is now generally available.

Custom metrics let you track specific events, actions, and measurements within your Forge app. This helps you monitor business KPIs and instrument critical paths in your app code.

Customers can enable or disable custom metrics access from admin.atlassian.com. The access status—enabled or disabled—now appears for each installation on the Installations page in the developer console. The default access is enabled for all installations.

Custom metrics are also available via the export app metrics API. For more information about metrics, see Monitor custom metrics.

We’ve introduced a platform-level URL persistence and redirect feature for apps migrating from Connect to Forge. Jira and Confluence will now accept legacy Connect URLs (including full path, query parameters, and fragments) and transparently redirect them to the corresponding Forge app module. For more information on how it works, please see the documentation here.