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 Cloud Platform.
For updates about changes to the Forge platform, see the Forge changelog in the Forge documentation.
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.
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.
We no longer support creation of Epic or Sub-task issue links with the create issue link REST API. This change was being made to streamline the API and improve performance.
This change has now taken effect following the published deprecation period.
We no longer support creation of Epic link or Sub-task issue links with the create issue link REST API.
Developers should use the parent field in the Issue API to create hierarchy relationships between issues.
API Reference: https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-links/#api-rest-api-3-issuelink-post
Parent field Reference: https://community.atlassian.com/t5/Jira-articles/Introducing-the-new-Parent-field-in-company-managed-projects/ba-p/2377758
Affecting the create issue link API
Stop specifying an Epic or Sub-task link type to the API. Epic or Sub-task link type is specified by setting type.name="Epic-Story Link",type.name="jira_subtask_link"or type.id="{linkTypeId}"where linkTypeIdis the id of the Epic or Sub-task link type.
This deprecation is complete. Requests that specify these fields will return a HTTP 400 bad request instead of the current HTTP 201 created response.
Note: All other link types will continue to work as-is.
Example payload that will become invalid
1
2
3
4
5
6
7
8
9
10
11
{
"inwardIssue": {
"key": "HSP-1"
},
"outwardIssue": {
"key": "MKY-1"
},
"type": {
"name": "Epic Link"
}
};Instead, provide the parent field to the Issue API (https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issues/#api-group-issues) for issues of all types to create a hierarchical relationship between issues. This is described in the existing notice here: https://community.developer.atlassian.com/t/deprecation-of-the-epic-link-parent-link-and-other-related-fields-in-rest-apis-and-webhooks/54048
An example new payload would be:
1
2
3
4
5
6
7
8
PUT /rest/api/3/issue/10054
"fields": {
...
"parent": {
"id": "10055"
}
...
}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
On February 18th, we announced that we will begin enforcing REST API (Quota and Burst based) rate limits for all free Jira and Confluence apps on or after August 18, 2025 and that we have added additional headers to provide further transparency.
To ensure Marketplace partners are able to decipher whether or not they’re facing actual rate limits, we have rolled out beta- prefixed headers. These will appear to notify partners that they would have breached the upcoming quota and burst based rate limits. The headers will be as follows:
Beta-Retry-After
X-Beta-RateLimit-NearLimit
X-Beta-RateLimit-Reason
X-Beta-RateLimit-Reset
However, if you do receive headers without beta-, be advised that you are facing rate limits.
Learn more about the new limits and headers for Jira here and Confluence here.
We are adding a Public access option to the forms available in Jira business and software projects. Any user, including those without a Jira license, will be able to make a submission through a public form. Jira admins will be able to disable public forms on their site.
An unlicensed user will be able to make a submission through a public form, but to view and collaborate on the work item created from their submission, they will need a Jira license.
There are no specific APIs or UI extension points currently available in Connect or Forge for forms. However, we would love to hear your feedback and ideas on how we could provide value for existing or new apps in the future on https://community.developer.atlassian.com/t/rfc-88-public-forms-in-jira/90181.
The deprecation of Epic link, parent link, and other related fields in REST APIs is now extended:
Parent Link will be removed on 13 June 2025
Epic Link will be removed on 13 September 2025
These fields have already been removed from webhooks and change history.
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.
Connect apps moving to Forge can opt-in to have their existing Connect installations updated to their latest Forge version, as long as they do not have an elevation in permissions. The rollout will be staggered over 96 hours by default, but can be further staggered via the staged migration process.
Until now, the first version of an app to adopt Forge features or migrate fully to Forge required admin approval in order to be upgraded on an existing installation site.
There are no changes in how updates work for apps that do not opt-in to this functionality.
Instructions on how to opt your app in to this feature and check its eligibility can be found at Minor version updates (Connect to Forge) (Preview).
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:
1
2
3
TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256
TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384For 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.
This update is based on a feedback ticket: JRACLOUD-40963 - Allow user filtering for User Picker (multiple users) custom field type
With this change, administrators can limit which users appear in User picker (multiple users) custom fields based on groups and project roles. This behavior mimics the same function found in Data Center versions of Jira.
As a result, user filter will be used as part of data validation when setting value through REST API for any fields of this custom field type.
Furthermore, inactive users will no longer be valid values of a User picker (multiple users) custom field. We recommend removing inactive default users of your User Picker (multiple users) custom fields to align with this change.
When admins enable filtering on any User Picker (multiple users) custom field, when a user selects a value validation ensures the user is an allowed value of the custom field, in addition to any other existing validation logic.
The validation error will change from:
Pick another user as the selected user doesn't exist.
to:
One or more of the selected users do not exist or are not valid for this user picker.
Rate this page: