This page includes release notes and updates for Jira Cloud app developers. Use this page to keep track of upcoming changes, deprecation notices, new features, and feature updates from Jira Service Management Cloud.
Go to our developer community to ask questions. You may also be interested in the What's New blog for Atlassian Cloud where details of major changes that affect all users of the Jira Cloud products are announced.
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.
For more details, read our FAQ
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.
To update your UI kit app to the latest version, run the following command in your project directory:
npm install --save @forge/react@latest
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.
Documentation on adopting Forge from Connect, capabilities equivalences between Forge and Connect, and other details about the transition from Connect to Forge for Jira and Confluence apps are available on the Adopting Forge from Connect content site.
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.
To update your UI kit app to the latest version, run the following command in your project directory:
npm install --save @forge/react@latest
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.
To improve performance and address constantly evolving threats on the web, Atlassian is enabling AWS Cloudfront Content Delivery Network (CDN) and Web Application Firewall (WAF) for all Confluence and Jira Cloud Customers.
A side effect of this change is the deprecation of the following three ciphers:
1TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256
2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
3TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
For the list of currently supported ciphers, please visit https://support.atlassian.com/security-and-access-policies/docs/supported-security-protocols-for-atlassian-cloud-products/ .
This change may impact 12+ year old systems under some conditions. Click more details for further information.
Windows Server 2012 (including R2) and Windows 8.1 native applications (such as Internet Explorer or Invoke-WebRequest) that rely on the inbuilt schannel may fail to interact with Jira and Confluence Cloud.
To resolve the problem, use an updated browser, including Chrome, Firefox, Edge, etc.
For curl and libcurl and other HTTP libraries, use a cross-compiled version that uses LibreSSL or OpenSSL.
Update to Windows Server 2016 or Windows 10 or later.
Alter your software to use an alternative HTTP/SSL/TLS library, or write it in a language which can use LibreSSL or OpenSSL or BoringSSL e.g. libcurl, Python, Node, Java, Go etc.
Add a small HTTP proxy between your application and Jira/Confluence Cloud (e.g. Nginx, HAProxy, Caddy, Traefik, Kong) that can negotiate TLS on behalf of your application. (Specific instructions on how to achieve this are not provided here).
Use the hosts file to pin your Jira/Confluence domain to our old IPs:
https://www.howtogeek.com/27350/beginner-geek-how-to-edit-your-hosts-file/
Note: These old IPs will only be available until October 2025.
US 104.192.142.18
Europe 185.166.143.36
Asia 13.200.41.128
For more information please see: https://community.atlassian.com/forums/Atlassian-Platform-articles/Windows-Server-2012-and-Windows-8-SSL-TLS-handshake-fails-with/ba-p/2967467#M152
Following the deprecation announcement on 28 Aug 2024, we have now removed UI Kit 1 from the Forge platform.
For apps still using UI Kit 1, customers will see that their app version is outdated due to a deprecated platform component.
You will need to upgrade to the latest version of UI Kit for your app to work. If you are in the process of upgrading your UI Kit 1 app, please refer to these resources to guide you through the transition:
UPDATE, 02 Mar, 2025 The scheduled upgrade was successfully performed on March 02, 2025 between 12:30 AM to 03:30 AM UTC, and we have verified that all the capabilities mentioned below are working as expected. If you are experiencing ongoing issues with these capabilities please contact your local Atlassian site administrator. If you need further help, please raise a support ticket at https://support.atlassian.com/#contact.
EDIT, 28 Feb, 2025 : Please note that below mentioned times are UTC i.e. 02 Mar, 2025 between 12:30 am to 03:30 AM UTC
Forge platform will be undergoing maintenance on March 02, 2025 between 00:30 AM to 03:30 AM. During this interval, below capabilities will not be available intermittently:
Create/update/delete apps
Deploy apps
Install/uninstall/upgrade apps
View existing installations
App invocations will continue to work for existing users of the apps. However, new customers might not be able to use apps as consent process will be impacted during this interval as well.
App activity logs are coming to Atlassian audit logs at the end of Feb 2025 for all admins with Atlassian Guard Premium or Cloud Enterprise licenses.
App activity logs record activity by third-party apps in the form of API calls to Jira and Confluence.
We will show app API calls for Connect, Forge and 3LO apps and related response code as well as information about whether the call was made asApp or asUser.
Admins will be able to search and filter for the app API logs through the audit log UI. To do so, they can use the ‘search’ bar or ‘activities’ filter.
Alternatively, admins can choose to register for a webhook to stream the API logs to their preferred destination for further analysis or integrate with a threat detection tool they may use.
Finally, there is also the option to use the audit log API to receive app activity logs
Rate this page: