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.
We’ve added a new REST endpoint that allows you to fetch configurations for multiple Forge custom fields at the same time.
We’re pleased to announce a preview release of support for a new location via the UI modifications extension point: Issue transition.
It’s the third Jira location to be supported, following the initial support for the Issue create modal and Issue view.
Documentation specific to the Issue transition is available under this link. The supported fields and methods are listed here.
To assign a UI modification to the Issue transition context, you need to pass a viewType equal to IssueTransition while creating or updating the UI modification. See more details in our REST API docs.
At the same time, we’re ending the UI modifications Issue transition Early Access Program. Your apps developed during the EAP will continue to work.
The UI modifications (UIM) module now supports the people field on the Issue view.
The complete list of supported fields for the Issue view is available here.
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.
In December 2023 we have announced a new limit coming to Connect field options and scopes: https://developer.atlassian.com/changelog/#CHANGE-1347.
This is a notice that we are going to begin rolling out this change beginning Sep 23, 2024.
The Connect field options and scopes API: https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-custom-field-options--apps-/#api-rest-api-3-field-fieldkey-option-post will introduce a maximum limit of 10,000 options for each field and a maximum of 10,000 scopes for each option.
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.
Rollout: Folders are currently in beta as of September 18 and will gradually go live for all customers in the coming weeks! In Progress
Endpoints and scopes have been added for Confluence Folders. For further information about these updates, reference the Atlassian Developer Documentation for OAuth and Forge scopes as well as Confluence Cloud REST API v2.
Three new scopes have been added for Folders: read, write, and delete. These additions will support the implementation of Folders in Forge applications.
Read | Write | Delete |
|---|---|---|
|
|
|
Creation, retrieval, and deletion of Folders have been added for v2 REST APIs. Creation, retrieval, modification, and deletion of properties as well as retrieval of operations and ancestors is supported via these added APIs.
Back in June, we announced a deprecation notice for the behavior of the parent field in the Edit issue metadata API. Starting on Sep 23, 2024, we will be rolling out these changes.
Previously, the parent field was always returned by this API regardless of screen configuration. These changes will mean that in company-managed projects, the parent field will only be returned in the response if the parent field is in the screen associated with the edit issue operation. The issue view experience will also be updated so that the parent field is only editable when it's on the screen associated with the edit operation. You can find more details here.
We’re aware that some customers currently rely on being able to edit the parent field regardless of their screen configuration. To ensure that these customers can continue to do so, the field has been added to the screen configured for the edit issue operation. Jira administrators can then remove the parent field from the edit issue operation screen if they wish to restrict its editing.
This capability allows a Connect app supporting data residency to remain in the same region which the app was originally installed for up to 30 days after uninstall. This allows customers to reinstall an app without suffering data loss by being pinned to a different region
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.
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}
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: