Changelog

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.

Transactions for KVS and Custom Entity Store is now generally available (including its REST API).

This feature allows multiple operations in a single transaction, ensuring that all operations are either committed or rolled back together if one fails. When used in the Custom Entity Store, you can add conditions to operations.

You can now declare a default value for environment variables in your manifest, which will be used if no environment variable is already exported. Read more about Variables.

We’ve increased the maximum number of resources that can be bundled with an app from 10 to 50. For more details, you can refer to the Forge resource limits.

The CLI linter was incorrectly adding an optional property to some existing egress permissions when it identified that certain permissions were defined using the simple string format.

This issue resulted in the manifest file being altered from:

to:

The latest version of the CLI fixes this problem and does not populate the optional inScopeEUD property anymore.

To install the latest version of @forge/cli and access these improvements, run the following command in your terminal:

To join this Early Access Program, please complete the Forge EAP sign-up form.

The Confluence Full Page UI module aims to enable developers to build fully custom, chromeless app experiences within Confluence Cloud, hosted directly on Forge.

To start using this EAP, sign up using the Forge EAP form.
For more information about how to use this module, see here.

As part of the Atlassian visual refresh updates, we updated the UI Kit Icon component. Some glyphs get a new look, and many more glyphs have been added. There are also a number of deprecations, as detailed below.