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.
A new RFC is ready for review at https://community.developer.atlassian.com/t/rfc-63-page-extension-in-editor-design-changes-and-more/83196/1 .
We have previously allowed the creation of priorities with an iconUrl parameter, which specifies the location of the icon image to be used when displaying the priority.
We are now moving towards using avatars, which will be uploaded using a separate API. Users will then be able to supply the avatarId to specify the avatar used when displaying the priority.
We are therefore deprecating the use of “iconUrl” as a parameter to the following REST APIs:
POST /rest/api/2/priority
POST /rest/api/3/priority
POST /rest/api/latest/priority
PUT /rest/api/2/priority/{ID}
PUT /rest/api/3/priority/{ID}
PUT /rest/api/latest/priority/{ID}
When making a request to:
POST /rest/api/*/priority
or
PUT /rest/api/*/priority/{id}
use avatarId instead of iconUrl.
Note to get an avatarId, use the Load avatar API to upload an avatar and get a avatarId.
e.g.
instead of:
1
2
3
4
5
6
{
"description": "My priority description",
"iconUrl": "images/icons/priorities/major.png",
"name": "My new priority",
"statusColor": "#ABCDEF"
}adopt the following request:
1
2
3
4
5
6
{
"description": "My priority description",
"avatarId": "1231",
"name": "My new priority",
"statusColor": "#ABCDEF"
}UI modifications, the Forge module that allows apps to modify fields, now supports the status field on the Issue view.
If your app uses granular scopes, it will need the following permission to access this field:
read:issue-status:jira
For more information, see the list of supported fields and read about granular scopes.
Rollout: progressive roll-out by request. COMPLETE
The extended period for deprecation of lenient URL path processing for OAuth 2.0 requests has now expired. This deprecation will be rolled out progressively over the next few days.
We're updating the limit for the maximum number of comments returned in a single API call from 5000 to 100 for all versions of the Get issue and Get comment operations.
This change will happen on Nov 22, 2024.
Requesting a lot of comments (more than 100) can cause out of memory exceptions.
If more comments are needed, the Get comments operation is better for retrieving large sets of comments as it contains pagination (more than5000).
If you are currently using any version of the Get issue or Get comments operations to retrieve more than 100 comments then you will receive a truncated list of comments. If more comments are needed, they can be fetched with pagination with the Get comments operation
This change will happen Nov 22, 2024.
We're announcing new IP ranges that will soon be available for requests from external clients, such as browsers and API integrations:
13.35.248.0/24
13.227.180.0/24
13.227.213.0/24
These ranges won't be used to make outgoing connections from Atlassian Cloud to remote systems, for example, webhooks.
To prepare for this change, update your firewalls and other security measures to allow connections to the new IP ranges.
For more information, see IP addresses and domains for Atlassian Cloud products, which includes instructions on how to receive notifications of changes, as well as links to machine-readable lists of our IP ranges.
We've released a substantial enhancement to the Connect Data Residency migration experience.
The Downtime Estimation feature is now in preview.
Marketplace Partners can now report the estimated migration downtime, ranging from 0.5 hours to 24 hours. This helps admins approximate the time to completion and coordinate operations while minimizing disruptions.
We're introducing new context variables for theissuelink_created and issuelink_deleted events.
These new context variables allow you to extend webhook URLs with the issue/project ID and key for both source and destination entities. To do so, use the following placeholders: {destinationIssue.key} {destinationIssue.id {destinationProject.key} {destinationProject.id} {sourceIssue.key} {sourceIssue.id} {sourceProject.key} {sourceProject.id}
Read more about variable substitution in webhooks here.
With the introduction of custom domains supported by Confluence, we’re adding a new attribute to the Server info API.
displayUrlConfluence - The active custom domain URL for Confluence.
Note: If a custom domain is inactive for Confluence, the system will revert to using the baseUrl as the default value.
Sample response after this change -
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
{
"baseUrl": "https://your-domain.atlassian.net",
"displayUrl": "https://instance.jira.your-domain.com",
"displayUrlServicedeskHelpCenter": "https://instance.help.your-domain.com",
"displayUrlConfluence": "https://instance.confluence.your-domain.com",
"version": "1001.0.0-SNAPSHOT",
"versionNumbers": [
5,
0,
0
],
"buildNumber": 582,
"buildDate": "2023-11-06T03:38:44.447+0000",
"serverTime": "2023-11-06T03:38:44.447+0000",
"scmInfo": "1f51473f5c7b75c1a69a0090f4832cdc5053702a",
"serverTitle": "My Jira instance",
"defaultLocale": {
"locale": "en_AU"
},
"serverTimeZone": "Australia/Sydney"
}Connect modules in Connect apps adopting Forge can now support internationalisation. The latest version of the connect-to-forge package will copy over the translations field in a Connect descriptor to a Forge manifest as connectModules.jira:translations or connectModules.confluence:translations based upon the product.
For more information, refer to Incrementally adopting Forge from Connect.
Connect modules in Connect apps adopting Forge can now support statically declared Cloud App Migration webhooks. The latest version of the connect-to-forge package will copy over the cloudAppMigration field in a Connect descriptor to a Forge manifest as connectModules.jira::cloudAppMigration or connectModules.confluence::cloudAppMigration based upon the product.
For more information, refer to Incrementally adopting Forge from Connect.
The Cloud App Migration support in apps adopting Forge from Connect will continue to only support the migration of Connect modules. For more details, please refer to Limitations and Differences.
Atlassian has discontinued support for data residency in Brazil for all products (Jira, Confluence, Jira Service Management, and Jira Product Discovery) effective on August 6, 2024.
We regularly review our investments to ensure they are aligned with our customers' top needs. As a result, we are reallocating resources to accelerate initiatives with higher demand across Brazil, such as adding customer-initiated keys to our BYOK solution and implementing granular data opt-out controls.
Action required:
Partners who currently leverage data residency in Brazil will need to deprecate their support, per the comms that were shared directly.
Any partners working on or planning to leverage this region should be aware of this update.
Atlassian remains committed to building secure, reliable, and compliant products that enable your teams to do their best work. Thank you for understanding and for your continued support.
The UI modifications (UIM) module now supports the affects versions field on both global issue create and issue view.
The complete list of supported fields per view can be found here.
As per CHANGE-1364, two new status codes (422 and 409) can now be returned by the following APIs:
POST /rest/api/{version}/issue (Create issue API)
POST /rest/api/3/issue/{issueIdOrKey}/transitions (Transition issue API)
PUT /rest/api/3/issue/{issueIdOrKey} (Edit issue API)
Refer to the earlier changelog for more details.
Rate this page: