Changelog

Support for Claude Opus 4.7 model is now available in Forge LLMs. For the exhaustive list of supported models, refer to our documentation here

Forge multi-entry resource bundles are now generally available in Jira and Confluence. This feature allows you to group multiple named entry points within a single resource, helping you optimise app performance and stay within resource limits.

What's changing
Multi-entry resource bundles allow you to define multiple entry points for a single resource in your Forge manifest. This is particularly useful for complex apps that need to share code between different parts of the UI while keeping the overall bundle size manageable.

What you need to do
To get started with multi-entry resource bundles, you can update your manifest.yml to include multiple entry points under a single resource. For more details, see the documentation here.

From Jul 8, 2026, we will begin removing the temporary restriction announced in CHANGE-3109 that required every update to Connect to Forge apps with over 50,000 users to be classified as a major version update. We will contact partners first before lifting the restriction on their app(s).

This restriction was introduced as a temporary safety measure to protect downstream Forge services from sudden traffic spikes during large version migrations. Since then, we have completed significant scaling and reliability work across the affected services, so we are now able to return these apps to the normal minor version update path.

• Affected Forge apps can return to using minor version updates, rather than being forced into major version updates and forge version bulk-upgrade batches.

• You will still be able to use forge version bulk-upgrade if you prefer a controlled, batched rollout - this remains available and unchanged.

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

To avoid any unexpected impact on in-flight migration activities, we will not automatically re-enable minor version updates for every affected app at once. Instead:

• We will contact affected partners individually to confirm whether you would like minor version updates re-enabled for your app, and to coordinate timing against your current migration plans.

• If you would like the restriction removed for your app now, please reach out to Ecosystem Support, and we will action the request.

What's changing

You can now control access for the jira:uiModifications module for different user types:

• Anonymous – users who are not logged in

• Unlicensed – users invited to a Jira space without a license (guests in case of Jira)

• Customer – JSM portal customers

By default, Forge apps only run for licensed Jira and Jira Service Management users. With this update, you can allow your UI Modifications app to run for anonymous, unlicensed, or customer users by declaring it in your app manifest.

What you need to do

To allow your app to work for anonymous, unlicensed, or customer users, add the unlicensedAccess property to the jira:uiModifications module in your manifest.yml file.

Only include the user types your app needs. For example, if your app only needs to work for anonymous users:

For detailed steps, refer to the https://developer.atlassian.com/platform/forge/access-to-forge-apps-for-unlicensed-users/.

What’s changing?

In preparation for the upcoming Developer Preview release of Forge Containers, access to the early access program (EAP) for this capability is now closed.

We want to thank everyone who participated in the EAP and provided valuable feedback. Your insights have been instrumental in shaping the next phase of Forge Containers.

What you need to do

If you are currently participating in the EAP, you can continue to use the feature.

If you missed the EAP, stay tuned to this changelog for the Developer Preview release announcement to start building with Forge Containers.

Forge apps that run entirely in the browser — with no backend resolver — can now emit custom metrics directly from the frontend. Previously, custom metrics were only available to apps with a server-side resolver.

What's new

• Frontend custom metrics — counter metrics can now be emitted from your app's browser-side code using the frontendCustomMetrics SDK in @forge/bridge available from v6.0.0 onwards.

• Metric limit doubled — to accommodate both backend and frontend metrics on the same app, the per-app custom metric limit has increased from 10 to 20.

Documentation

See Instrument a frontend custom metric for the full API reference and setup guide.

What’s changing?

As previously announced in CHANGE-3120, usage of asynchronous Forge functions is now billed in line with Forge platform pricing.

Billing will be enabled progressively for all apps commencing Jul 2, 2026, with charges commencing in invoices issued from Aug 1, 2026 onwards.

What do I need to do?

No action is required. However, you should review your forecast usage in the Usage and Charges section of the Forge developer console.

Forge Rolling Releases is now available in Preview. This feature allows app developers to continuously deploy code updates to all eligible installations, even when new permissions are involved.

Getting started:

1. Add enforcement: app-managed to your manifest's permissions section

2. Implement the Permissions SDK to check permissions at runtime

3. Run forge deploy: a rollout will start automatically, or use --no-rollout and manage rollouts from the Developer Console

The new rollouts tab in the developer console is progressively rolling out over the coming days. If you don't see it yet, check back shortly as access is being expanded incrementally.

For full details, see https://developer.atlassian.com/platform/forge/rolling-releases/.

The new customerServiceManagement:crmImport Forge module is generally available from June 30, 2026.

What's changing

This module allows you to add an item under the Manage dropdown on the Customers, Organizations, and Products pages within the customer directory of the Customer Service Management (CSM) app. When a user clicks the item, your app renders content inside a modal dialog.

This extension point is specifically designed for apps that import customer context data from external CRM systems into Customer Service Management, providing a dedicated UI entry point for these integrations.

What you need to do

To start using this module, refer to the customerServiceManagement:crmImport manifest reference for technical configuration and schema details.

What is changing?

We previously announced that usage of asynchronous Forge app invocations will become billable on Jul 1, 2026.

To compensate for the inclusion of these functions in your billable usage, we are doubling the free usage allowance for Forge functions from 100,000 GB-seconds per month to 200,000 GB-seconds per month.

The increased allowance will be rolled out progressively, for:

• Newly-created Forge apps starting on Jun 29, 2026

• Existing Forge apps starting on Jul 1, 2026

The increased allowance will apply for all apps for the billing month of July 2026.

What do I need to do?

No action is required. The increased allowance will be applied automatically.

We recommend reviewing your Forge functions consumption in the Forge Developer Console's Usage and Charges section to understand how this change affects your apps before billing begins.

Forge Realtime has moved from Preview to General Availability. You can now use Realtime in production apps with full platform support and operational readiness.

What's changing

• Distinct subscriber and publisher roles: You can now issue tokens that grant only subscribe or publish access to a channel using the new permissions argument in signRealtimeToken. This lets you restrict publishing to your backend while granting subscribe-only access to frontends. Tokens without explicit permissions remain with full access.

• Rate limits: Limits of 50 operations per app installation per second are now enforced. See Realtime limits and error messages for details.

What you need to do

• Run the following commands in your app directory to install the latest versions of these packages:
   npm install @forge/bridge@latest
 npm install @forge/realtime@latest

The global:ui module is now available through the Early Access Program (EAP). This module allows your Forge app to have its own end-to-end experience within the Atlassian platform, independent of specific product contexts like Jira or Confluence.

What's changing

The global:ui module enables your app to:

• Deliver a full-screen experience with side navigation that you control and top navigation provided by the Atlassian platform.

• Appear in the Atlassian app switcher, allowing users to reach your app from anywhere in the platform.

• Connect to one or more Atlassian apps through multi-app compatibility, and optionally surface data across them.

• Build on platform capabilities such as Teamwork Graph, Forge Agents, Rovo Search, and Rovo Chat.

What you need to do

To start building apps with the global:uimodule:

• Join the EAP by completing the sign-up form.

• Review the detailed documentation.

Forge Object Store billing will be rolled out in stages starting June 29, 2026. While most existing apps won't see changes until July, new apps created during the transition window will have billing enabled immediately.

What’s changing

• Existing Forge apps: Object Store becomes a billable capability starting from your billing cycle on July 1, 2026. You will not see charges for Object Store usage before this date.

• New Forge apps: For any apps created on June 29, 2026 or June 30, 2026, Object Store is billable immediately upon creation. Charges will apply if your usage exceeds the free quota during this window.

What you need to do

• Review the Forge pricing guide to understand the free quota and pricing for Object Store.

• If you are planning to create new apps on June 29 or 30, factor in the immediate billing activation for Object Store.

For more context on the Object Store release, see the Forge Object Store is now in Preview changelog entry.

We've added new convenience components and hooks for routing in UI Kit. These are now available in Preview in the latest version of @forge/react.

Routing is available in any full-page module and enables your app to manipulate the current page URL using a familiar API.

What’s changing

You can now use the following components and hooks to manage navigation within your Forge apps:

• Router

• Route

• useNavigate

• useLocation

• useParams

What you need to do

To use these new features, update to the latest version of the @forge/react package. In your terminal, run the following command from your project directory:

npm install --save @forge/react@latest

For implementation details and code examples, refer to the documentation links above.

We've added a new Forge module (devops:securityInfoProvider) that lets your app send security information (such as vulnerabilities and security containers) to Jira and associate it with issues. This is now available in preview.

What's new

The devops:securityInfoProvider module surfaces your app's security data directly in the development panel of Jira issues. Apps can write and delete security information using the https://developer.atlassian.com/cloud/jira/software/rest/ via the requestJira function.

To register a provider, declare the module in your manifest.yml and configure the required endpoint handlers:

• fetchWorkspaces: returns the list of workspaces available to the user

• fetchContainers: returns security containers within a workspace

• searchContainers: searches containers matching a query

Two optional lifecycle hooks are also available: onEntityAssociated and onEntityDisassociated, invoked when a container is linked or unlinked from a Jira entity.

Important behaviour to note

When a user uninstalls your app, all security data your app sent to Jira is deleted after a grace period.

There is currently a limitation, where your Forge app must define a Connect app key in order to be able to link workspaces. See https://jira.atlassian.com/browse/ECO-1602

Get started

See the https://developer.atlassian.com/platform/forge/manifest-reference/modules/jira-software-security-info/ for the full manifest schema, example requests/responses, and property details.