Changelog

The previous announcement for Project/Fields Association Improvements for team-managed projects has been updated to clarify that all fields are affected by the change and not just user-created custom fields.

Re-read the announcement by visiting https://developer.atlassian.com/changelog/#CHANGE-2278

Internationalization (i18n) for Forge apps is now generally available. This allows you to add translation support to your app so that it can adapt based on a user’s language and locale.

In addition to the Confluence and Jira modules that were supported during the EAP, internationalization support can now also be added to Bitbucket, Compass, and Jira Service Management modules, as well as Forge resolvers.

For more information, see Internationalization.

After our announcement in June 2024, we’ve now successfully completed the migration of Forms (previously ProForma) data from Jira entity properties. This will now enable us to build new functionality and increase performance and reliability of Forms.

Starting May 1 2025, we’ll begin removing access to historical Forms data available via Issue properties routes and Project properties routes in order for us to complete post-migration work.

You will still have full access to your Forms data though the Forms REST API.

If you’re currently using Jira Issue entity property smart values to access Forms data in Automation, we will continue to support this however we encourage you to consider moving any Automation to our new Forms smart values.

Forge Remote Data Residency realm migrations is now available in GA. This release provides apps with the ability to support customer-initiated migrations between data residency regions.

Please review the documentation to learn more about how to support realm migrations in your app.

The extension context now includes navigation details that indicate whether a customer is viewing the new or old navigation system, represented by the structure { "jira": { "isNewNavigation": boolean } }, for all Jira Forge apps. This allows developers to customize their Jira Forge apps according to the type of navigation the customer is using.

We will not be issuing any new waivers for apps that need to request or store Atlassian user API tokens. This decision is part of our ongoing commitment to enhancing security and protecting customer trust.

Forge Apps that have already been granted waivers must ensure a lack of alternative solutions within Forge. They can continue to operate, but no additional waivers will be granted for new modules or new functionality within the same app.

Connect apps that have been granted waivers and any existing Connect app requesting or storing Atlassian user API tokens are required to migrate to Forge, with tokens stored in Forge encrypted storage.

We have updated our UI Kit components, Text and Heading to make them more flexible:

Text

• Now supports align, as, color, maxLines, size and weight properties.

For more information, see Text component documentation.

Heading

• You can now control how the Heading component appears by setting a value for size, while the as prop controls the HTML element's rendering.

For more information, see Heading component documentation.

In the latest version of @forge/react, we're adding a new disableSubmitOnBlur property to the UI Kit Jira component, CustomFieldEdit. The property can be used to disable the submission of the field value on blur events.

For more information on this component, see the component documentation.

Connect to Forge now supports the migration of the global and permission modules. For more information, see: https://developer.atlassian.com/platform/adopting-forge-from-connect/migrate-jira-global-project-permissions/

After the beta phase of Atlassian’s new navigation, we’re thrilled to announce its General Availability (GA) for Jira, Jira Service Management, Jira Product Discovery, Confluence, and Atlassian Home. In this article, you’ll find key details about what’s changing with the new navigation, Jira and Jira Service Management apps, as well as when those changes will go live.

Starting Sep 17, 2025, the ability to publish a new Jira or Confluence app using a JSON Connect descriptor to the Atlassian Marketplace will be deprecated. This change is part of our strategic shift to the Forge platform that enables developers to leverage enhanced capabilities such as Forge Storage.

Partners should plan to list any Connect apps currently under development on the Atlassian Marketplace by Sep 16, 2025, and should undertake all new app development on Forge.

Today we published Announcing Connect End of Support: Timeline and Next Steps, following up on our earlier blog post Taking the Ecosystem Forward: An Update on the Future of Connect.

This announcement is intended for developers of Connect apps, including partners and customers with custom apps. It provides a detailed view of the phases and timing for the end of support of Connect.

In the latest version of @forge/react, we're adding a new disableSubmitOnEnter property to the UI Kit Jira component, CustomFieldEdit. The property can be used to disable the submission of the field value when the “Enter” key is pressed.

For more information on this component, see the component documentation.

Forge Remote Data Residency realm migrations is now available in Preview. This release provides apps with the ability to support customer-initiated migrations between data residency regions.

Please review the documentation to learn more about how to support realm migrations in your app.

All data residency migration lifecycle requests will now include an additional migrationId field to support improved tracking, reporting and monitoring of migration requests.