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.
We are removing mirrors of third-party packages such as maven-central from packages.atlassian.com
We're updating how we provide packages for customers and partners to develop with our platforms. Starting February 1, 2025, we will discontinue providing third-party packages on packages.atlassian.com. Instead, customers and partners must fetch these packages directly from the original upstream repositories.
For details on how this change affects you and for guidance on migration, please refer to the documentation available at http://developer.atlassian.com .
The Atlassian Connect in Jira Cloud project in the Atlassian Ecosystem Jira tracks issues with Atlassian Connect in Jira and its REST API. To improve response times, we’re no longer accepting new issues in this Jira project as of this announcement. Instead, we encourage our partners to file issues with Developer and Marketplace support.
The Jira and JSM cloud navigation changes as previously mentioned are now available in EAP. This Early Access Program will enable partners to test the new navigation and assess how apps will adapt to the proposed changes.
As part of EAP, we’ve set up a dedicated group on CDAC where you’ll be able to discuss these changes. Please note that the designs in the EAP are not final, so you are NOT expected to make any changes to your apps during the EAP. For partners who previously expressed interest, the new navigation will be activated to the test instances today.
To join this Early Access Program, register using the EAP form.
See RFC-45 for more information on Jira and JSM Cloud navigation changes
We are making the following change to the REST API’s for Assets in Jira Service Management Cloud:
We will be removing the summable attribute from the request/response payload of the following endpoints:
/object (response)
/objectschema (response)
/objecttype (response)
/objecttypeattribute (request/response)
This change will be made on or after 31 Jan 2025.
When updating a Jira project via the API, you can now release project keys so that they can be reused. To do so, pass releasedProjectKeys as an array of keys to release. There are two conditions before you release a project key:
Released keys must belong to the given project.
Released keys must not contain the currently active project key.
In addition, there are caveats to releasing previous project keys such as that any links, filters, queries, and marketplace apps which use your previous keys might no longer work.
As discussed in RFC-45, there are upcoming changes to Jira and JSM Cloud navigation. As a result, you may want to trial the navigation changes and assess how your apps will adapt to the proposed changes.
To participate in the upcoming Early Access Program (EAP), please provide your Jira/JSM test instance details via the EAP waitlist form. This will give access to the EAP version of the new look of Jira and JSM. We will notify you about your enrollment once the EAP launches on October 14, 2024.
This EAP will give the opportunity to test the navigation changes, understand the direction Jira products are heading in, and share your feedback. As part of EAP, we’ll set up a dedicated group on CDAC where you’ll be able to discuss these changes. Please note that the designs in the EAP are not final, so you are NOT expected to make any changes to your apps during the EAP.
Forge custom fields on the Issue view will render inline in edit mode by default from Apr 1, 2025 (6 months from this announcement).
During the transition period, you can use the isInline property in the app manifest to enable the inline edit mode for apps built with UI kit and Custom UI. You can read more about custom field rendering in the Forge documentation. After the deprecation period, rendering fields in the modal will be possible only using the dedicated UI kit modal component or Forge bridge API.
In the latest version of @forge/react, we're releasing a new UI Kit product-specific Jira component, CustomFieldEdit, which can be used to offer inline editing for Forge custom fields.
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
We’re launching the new Forge Roadmap, updated every hour with the latest insights from our internal Jira Product Discovery. Developers and partners can use this roadmap to stay informed about upcoming features and changes. If you have feedback, share it in our community thread.
Forge apps can now access the Get User Email and Get User Email Bulk APIs on Jira and Confluence when declaring the read:email-address:jira or read:email-address:confluence scopes.
Access to the Get User Email and Get User Email Bulk APIs is only supported when making asApp() requests. Requests made asUser() are not compatible with these APIs.
Learn more about profile visibility on Forge apps here.
Following its preview release back in February, Adopting Forge from Connect is now generally available.
The majority of apps can now incrementally adopt Forge with their existing Connect apps. The remaining apps will be able to do so when Data Residency support is available for Forge Remotes.
Learn more in our blog post - Connect apps will gain new extensibility features through Forge
Existing Connect apps now have a simpler, automated and incremental pathway to adopt Forge capabilities. This release includes:
Automated tooling to support the conversion from Connect to Forge
Support for immediate version updates of Forge apps containing connectModules
Increased compatibility for the types of connectModules that can be declared within a Forge manifest
Support for Forge Remote Compute (preview) in the Atlassian Connect Express (ACE) and Connect Spring Boot (ACSB) frameworks.
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}
There is a deprecation period of 6 months, finishing on Mar 4, 2025.
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"
}After 31st of October 2024 we will be introducing a new limit of 2 unique constraints per object type. For customers with any existing object types that already have more than 2 unique constraints, we are asking these customers to please reduce these to 2 per object type before 31st of October 2024.
At present an object type in Assets for Jira Service Management can have an unbounded number of unique constraints applied to its attributes. After 31st of October 2024 we will be introducing a new limit of 2 unique constraints per object type. This is part of our effort to offer a more scalable, performant and reliable experience as we make major enhancements to the underlying platform that powers Assets. We believe this new limit will be sufficient for the vast majority of use cases in which Assets is utilised.
For customers with any existing object types that already have more than 2 unique constraints, we are asking these customers to please reduce these down to 2 per object type before 31st of October 2024. Not doing this will mean:
When we are ready to begin moving you to the new Assets platform, we will be unable to do so without first disabling your unique constraints on any object type with more than 2.
You will be able to re-enable up to 2 per object type after this is completed.
More information on this process will be released in future.
Effected public Assets REST API endpoints are:
Both of these endpoints will begin to return a HTTP status code of 400 if there is an attempt to add a unique attribute constraint (via the uniqueAttribute property) and the limit has been reached.
If you have more than 2 attributes on an object type that you need to ensure are unique, a potential workaround is creating an automation rule to check the number of objects that can contain a particular value after an object is updated. You could then raise a Jira issue to resolve the duplicate or notify the relevant schema administrator.
By making these changes we can ensure your site can begin to utilise our improved Assets platform when it is completed and reap the vastly improved the scalability, performance and reliability it will offer. We’ll be announcing more about this soon.
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 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.
Rate this page: