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 Software 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 navigation changes to Jira, JSM, JPD, and Atlassian Home have now moved from EAP to Beta. For partners, this is an extension of the previously announced EAP. This extended EAP will enable partners to test the new navigation and assess how apps will adapt to the proposed changes. Unlike the previous EAP, the design direction is now near final, so we recommend partners start adopting the new navigation.
As part of the extended EAP, we’ve set up a dedicated group on CDAC where you can discuss these changes. To join the beta launch, register through the EAP form.
Please visit the community post https://community.atlassian.com/t5/Navigation-Refresh-articles/What-s-changing-in-Apps-with-Atlassian-s-Beta-launch-of-New/ba-p/2871925 where you will find detailed information about the changes, recommendations, and a comprehensive FAQ section tailored for our partners.
Progressive Rollout: This change will be applied to all sites over the coming weeks.
Following the previous deprecation notice, changelogs for Epic Link and Parent Link field values are no longer available from Jira Cloud REST API. We recommend using the IssueParentAssociation changelog items instead.
For webhooks in Jira, we recommend consuming the IssueParentAssociation items, as mentioned in this community announcement (see Change 6).
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.
We’re happy to introduce new Jira Software Forge product events for boards:
board created - avi:jira-software:created:board
board updated - avi:jira-software:updated:board
board deleted - avi:jira-software:deleted:board
board configuration changed - avi:jira-software:configuration-changed:board
Follow the link above to read more about them.
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
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
Internationalization (i18n) for Forge apps is now available under Forge’s Early Access Program (EAP). Internationalization allows you to add translation support to your app so that it can adapt based on a user’s language and locale.
To start using this EAP, sign up using the Forge EAP form.
For more information about how to internationalize your app, check out the internationalization documentation.
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"
}Rate this page: