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 AdfRenderer component provides a way to render a valid ADF document, using the same renderer that Atlassian uses internally to render ADF content in Confluence pages, Jira work items, and so on. See ADF renderer for the full docs.
The ADF renderer component also allows you to replace node types that are unsupported in the context of a Forge app with replacement content, or remove them entirely.
See Atlassian Document Format for information on valid nodes.
Run npm i @forge/react@latest to install the preview version of the components and try them out now.
We have now removed the UI Kit @forge/react version 9 from the Forge platform. This UI Kit version was deprecated on Aug 28, 2024.
We recommend using the latest version of UI Kit (@forge/react10).
For more information, see our deprecation policy.
The non-public endpoint /rest/teams/1.0/teams/find will be removed as part of the changes coming to Teams. This change is necessary to streamline our API offerings and improve performance. This change will take effect 3 months from this notice 05 Mar 2025.
If you have integrations with this internal API endpoint, migrate your system to use the teamSearch GraphQL query instead.
We’ve added the jira:issueNavigatorAction module to Forge. You can use it to create custom actions on the issue navigator view. For more details, see the Jira issue navigator action documentation.
To be able to use the new module, you must first update the Forge CLI: npm install -g @forge/cli@latest
We’ve just introduced multiple new display conditions for use with Jira Forge modules, including conditions for checking entity properties. The new arrivals also include conditions for app licenses and permissions, as well as the powerful Jira expression condition. We’re happy to say that, with this change, Forge display conditions have now reached feature parity with Connect.
See more details in the documentation: Display conditions.
As of today, version 3 of the Jira REST API has been promoted to general availability(GA). We are updating the classification to more accurately reflect the stability and production readiness of the v3 API.
The official recognition of version 3 of the Jira REST API as Generally Available (GA) provides greater clarity for developers regarding the API’s usage in production scenarios.
This announcement doesn’t affect the functionality of either the v2 or the v3 API, so there’s no action required from you.
There are currently no plans to deprecate v2; we will continue to provide general availability-level support for both the v2 and v3 APIs.
We now accept bug and incident reports under a single new request type: Ecosystem Support Request. This change simplifies the process of reporting issues to our support team, so that we can handle your issue more efficiently, and ensure consistent handling for all critical issues, particularly incidents.
We’ve also detailed the scope of our Developer and Marketplace support, so you have a better understanding of supported issues and response times.
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.
Rate this page: