Changelog

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.

We have now added the ability to use the following as dynamic modules, available under Forge’s Early Access Program (EAP):

• Issue Action

• Issue Activity

• Issue Panel

• Issue Context

• Custom Field

• Custom Field Type

• JQL Function

• Entity Property

To start testing, sign up for the EAP here.

The KVS and Custom Entity Store now allow you to batch multiple delete and get operations. These new capabilities are included in the latest version of the @forge/kvs package.

You can now generate Atlassian API tokens that are scoped to only the permissions required for the Forge CLI. Update to Forge CLI version 12.15.0 or later to start using scoped tokens.

Previously, Forge CLI relied on tokens with broad permissions. Scoped tokens help you follow security best practices, apply the principle of least privilege in CI/CD pipelines, and reduce the blast radius of a compromised token.

What you need to do

1. Update your Forge CLI to version 12.15.0 or later.

2. Run forge login and follow the instructions to create a Forge scoped API token.

Existing unscoped tokens will continue to work.

The Forge Model Context Protocol (MCP) Server is now generally available. This remote MCP server enables Forge app developers to use coding agents with up-to-date Atlassian Forge and Cloud documentation, including markdown-based guides, module catalogs, and manifest references. The Forge MCP Server also offers a search feature for Forge reference documentation and implementation patterns. These features are designed to streamline Forge app development in AI-powered workflows.

This release packs performance, reliability and search relevance improvements. We invite you to try the Forge MCP Server and share your feedback to help us improve.

We've introduced three new Forge triggers for Bitbucket deployment events. These triggers allow your Forge app to respond to deployment lifecycle events in Bitbucket Pipelines.

The new triggers are:

• avi:bitbucket:pending:deployment — Fires when a deployment is pending

• avi:bitbucket:started:deployment — Fires when a deployment starts

• avi:bitbucket:completed:deployment — Fires when a deployment completes

To use these triggers, add them to the trigger section of your app's manifest.yml file. Each trigger provides deployment event data including environment, state, and pipeline details.

For more information, see Bitbucket events.