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.
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.
We are making changes to the ObjectTypeAttribute and ReferenceType response payload for all endpoints within the REST API’s for Assets in Jira Service Management cloud.
We will be removing the objectAttributeExists attribute from the ObjectTypeAttribute response payload across all endpoints.
We will be removing the removable attribute from the ReferenceType response payload across all endpoints.
These changes will be made on or after Jan 31, 2025
In the interest of performance, we will be removing support for the objectAttributeExists attribute from the ObjectTypeAttribute response payload and the removable attribute from the ReferenceType response payload for all endpoints. The following endpoints are affected:
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.
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.
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.
Rate this page: