Rate this page:
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.
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.
JQL queries containing issuekey or issue will have the error messages and response code changed.
See the full announcement here
Atlassian is standardizing how issue type hierarchies are created and configured across the Jira product suite. As a consequence, several REST API operations will cease to report a hierarchy level on issues from 1 November 2021.
See Deprecation notice: Hierarchy level changes for more detail.
A breaking API change will be made to Atlassian Connect in Jira and Confluence Cloud to mitigate a vulnerability in the verification of the claim in Connect JWT authentication. The change affects apps that specify an authentication descriptor setting of .
Classic and next-gen projects in Jira now have new names that are clearer and more descriptive of their corresponding project types:
JQL clauses using custom fields of types and will no longer be supported as of 01 October 2021.
From 5 April 2021, we're introducing a permission check to the GET avatars operation when fetching issue type avatars. Custom avatars are only returned if the user has the Browse projects project permission for at least one project the issue type avatar is used in.
Additionally, when trying to view a custom issue type avatar using the path, if the user doesn't have the required permission the appropriate system default avatar is returned.
See Adding browse project permission check for viewing custom issue type avatars for more detail.
We are removing hierarchy level IDs and entityIDs from next-gen project APIs. Jira will stop returning id, entityId, entityUuid, baseLevelId, aboveLevelId, belowLevelId, and projectConfigurationId on 1 September 2021.
For more details see Change notice: Removing hierarchy level IDs from next-gen APIs
Some operations of the Issue custom field options resource have been replaced with new versions. As a result, the legacy operations in the Issue custom field options resource will be removed on 8 May 2021.
See Removal of custom field options operations for more detail.
On 22 October the path of experimental operations Get options for field (context),
Reorder options (context)
and Delete custom field option (context)
changed from to . Also, the format of changed to 'customfield_xxxxxx'.
Commencing on 16 June 2020 and rolling out over two weeks Connect app security is being enhanced by ensuring old values can not be used.
See Enhanced Validation of OAuthClientIds for more detail.
From 1 April 2020 the Connect App iframe security is being improved by the sandboxing of various features.
See New sandboxing of Connect App iFrames for more detail.
On 10 September 2020 the following legacy fields will be removed fron the Connect app install payload:
See Removal of some Connect App install payload fields for more detail.
From 1 September 2020, Jira REST API responses that include the Sprint custom field type will no longer return string representations of sprints in the body.
See toString representation of sprints in Get issue response for more detail.
Some time after 4 May 2020 calls to Transition Issue blocked because another issue transition is being executed will return the status code with 409 (conflict) rather than a 400 (bad request).
See Update in simultaneous transitions of an issue via API for more detail.
From 22 Aug 2019 the spacing between Jira’s navigation sidebar and vendor applications is increased by 20px.
See Padding update for Jira Cloud navigation UI for more detail.
From 16 January 2020 it will no longer be possible to disable time tracking in the Jira Cloud UI and Jira Cloud REST API.
See Removal of the ability to disable time tracking for more detail.
From 3 December 2019 it will no longer be possible to change project type in Jira Cloud via REST APIs.
See Updating project types using the REST API for more detail.
and fields in GET /rest/api/2/search now return a maximum of 1000 entries.
See GET search optimized for fields and for more detail.
By 29 April 2019 data used to identify users, such as and , will be removed from the REST API and replaced by the Atlassian account ID ().
From 1 April 2019 the paginated operations for filters and projects must be used.
See Removal of non-paginated project and filter endpoints from REST API v2 for more detail.
From 1 April 2019 encoding of some characters used in REST API calls will be required.
See Required encoding of some characters used in REST API calls for more detail.
By 31 December 2018 support for non-secure URLs for registered webhooks will be removed.
See Registering webhooks with non-secure URLs for more detail.
From 1 February 2019 the query parameter will be required in all requests to the Get my permissions operation.
See Get my permissions resource now requires the permissions query parameter for more detail.
From 3 September 2018 REST API requests to create a board will require a location.
See Location will become a required field in board creation for more detail.
Basic authentication with passwords and cookie-based authentication will be removed in 2019.
See Basic authentication with passwords and cookie-based authentication for more detail.
As the new Jira Cloud experience rolls out, several locations for providing content in the Jira Cloud user interface have evolved and been replaced with new APIs. The items removed are the project tab panels, profile tab panels, and project admin summary panels.
See Removal of web fragment locations in new Jira Cloud experience for more detail.
Rate this page: