Changelog

Forge now supports migrating custom content modules from Connect to Forge while preserving existing content. Add the migratedFromConnect: true to your custom content module to maintain compatibility with existing Connect content.

See the documentation for more details.

Forge offline user impersonation was recently made available in Preview. As part of this, the ability to exchange a Forge system OAuth token on a Forge remote for a token to impersonate any user.

This was released with a rate limit of 10,000 requests per minute per app, however after carefully consideration, we need to temporarily reduce this limit to 1,000 requests per minute per app. This rate limit applies only to the exchanging of a system token for a user impersonation token using the offlineUserAuthToken GraphQL mutation. Calls from a Forge function using asUser are not affected. Calls made to APIs using these tokens are not affected and instead use the rate limit defined for each API endpoint

We will continue to work towards increasing this limit as we move towards general availability of this feature.

To address parity gaps between Connect webhooks and Forge product events in Confluence, the following changes have been made for various events:

The space.homepage field hasn’t been added to space events due to an unexpected issue. We will add it as soon as we resolve the problem on our end. However, the ID of a space homepage can still be retrieved via the https://developer.atlassian.com/cloud/confluence/rest/v2/api-group-space/#api-group-space.

For more details on the Forge product events, refer to https://developer.atlassian.com/platform/forge/events-reference/confluence/ page.

The nodejs18.x runtime available to Forge apps has reached the end of its deprecation period, and is no longer supported.

Apps using this runtime can no longer be deployed or updated, although existing deployed apps may continue to function. Such apps are provided “as-is", with no warranties or access to support. Over time, unsupported runtimes may become non-functional or vulnerable to security issues.

All app developers are strongly encouraged to update their app to a supported Node.js runtime (nodejs20.x or higher) as soon as possible.

The Teamwork Graph Smart Links module is now available in Forge, allowing developers to create custom Smart Links that enhance URLs with additional metadata, thumbnails, and status indicators.

This feature enables rich link previews and improves user experience by providing contextual information and actions for linked content from supported platforms.

For more information, see Smart Link module documentation and Teamwork Graph supported object type documentation.

The Smart Links module is currently only available for apps installed into Jira.

We've updated the Forge module jira:projectPage to include board.id and board.type in its extension data. This change allows developers to access board-specific information directly within the project page, enabling more tailored and context-aware apps.

A new RFC is ready for review at https://community.developer.atlassian.com/t/rfc-101-forge-billing-developer-space-roles-and-permissions/94049

On Jul 27, 2025 from 10:00-13:20 UTC, we will be migrating our Custom Entity Store metadata to a new data source. During this time, the following commands will fail for any apps that have storage:entities declared in their manifest:

• forge deploy

• forge storage entities indexes list

KVS and Custom Entity Store operations will continue to work as normal.

We are announcing support for the following Forge Jira Software provider modules. More information can be found in our documentation: https://developer.atlassian.com/platform/forge/manifest-reference/modules/index-jsw/

• devops:developmentInfoProvider

• devops:featureFlagInfoProvider

• devops:deploymentInfoProvider

• devops:buildInfoProvider

• devops:remoteLinkInfoProvider

Forge CLI version 12.2.0 is now available. We have updated the deprecated dependencies so that when you install this version of the CLI, you won’t see any deprecation warnings.

For more information on installing and upgrading the Forge CLI, visit our reference page.

The following UI Kit components are now generally available:

• https://developer.atlassian.com/platform/forge/ui-kit/components/adf-renderer/

• https://developer.atlassian.com/platform/forge/ui-kit/components/calendar/

• https://developer.atlassian.com/platform/forge/ui-kit/components/checkbox-group/

• https://developer.atlassian.com/platform/forge/ui-kit/components/empty-state/

• https://developer.atlassian.com/platform/forge/ui-kit/components/inline-edit/

• https://developer.atlassian.com/platform/forge/ui-kit/components/list/

• https://developer.atlassian.com/platform/forge/ui-kit/components/popup/

• https://developer.atlassian.com/platform/forge/ui-kit/components/time-picker/

No code changes are required. These components will now follow the 6 month deprecation period if any breaking changes were to be made.

When an app moves from Connect to Forge today, developers can opt-in to automatically roll out the Forge version to existing Connect customers. Following the introduction of Forge bulk-upgrades, from Aug 18, 2025 the first update from Connect to Forge will now automatically rollout to customers when an app is eligible. Rollouts will now also occur over a 120 hour (5 day) period, rather than the existing 96 hours utilised during the preview.

Apps which have already moved from Connect to Forge and have not opted in for this behaviour will see customers progressively updated if their latest Forge version is eligible from Aug 18, 2025.

We've introduced support for all Forge custom field types on the Jira Service Management portal view. This update allows you to specify the portal-view experience in the view entry point when using UI Kit for app rendering. The goal is to improve the flexibility and functionality of custom fields in the Jira Service Management portal.

Additionally, Forge custom fields on Jira Service Management portal requests are now generally available.

We're also introducing unlicensed access support for Forge custom fields on the Jira Service Management portal. Documentation for it can be found here: https://developer.atlassian.com/platform/forge/access-to-forge-apps-for-unlicensed-jsm-users/.

We’re launching a Forge module to allow extension of the new home dashboards that are currently in open beta. This early access program (EAP) will enable partners to test the new module, and provide feedback and requests.

We plan to run this EAP for roughly 3 months and we are particularly keen to hear what is missing from the module and the additional areas of extensibility we can provide.

As per the Atlassian Developer Terms, EAPs are offered to selected developers for testing and feedback purposes. APIs and features under EAP are considered “Early Access Materials” (set forth in section 10 of the Atlassian Developer Terms) and are unsupported, subject to change without notice, and are not recommended for use in production environments.

To participate, please sign up for the EAP here.

We are removing documentation for internal APIs from public docs for graphql APIs (from Connect Service section). These APIs are meant to be used by Atlassian experiences only and we do not support these APIs for public consumption.