Last updated Mar 29, 2023

Rate this page:

Changelog

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.

Forge changelog

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.

29 March 2023

Added Adding a `products` field to the Jira create user REST API

We’ve added a new field, products, to the Jira create user REST API.

This field allows customers to create new users with explicitly defined access for different products. Until now, new users could only be created with default product accesses.

28 March 2023

Deprecation Notice UI modifications changes to setValue and getValue contracts

In the UI modifications module, the contract and signature for the setValue and getValue methods will be deprecated. The following fields will be affected: 

All of the deprecated contracts and signatures will be removed after June 28, 2023.

For more information on what changes should be done prior to the deprecation end date, see the list of supported fields.

More details

List of changes:

  • priority

    • setValue the available argument type is string, values represent option ID

  • assignee

    • setValue the available argument types are string and null, values represent account ID

    • getValue the properties displayName and avatarUrls are deprecated and will be removed

  • single select

    • setValue the available argument types are string and null, values represent option ID

    • getValue the returned option shape name property is deprecated in favor of the value property

  • multiple select

    • setValue the available argument type is string[] , values represent option IDs

    • getValue the returned option shape name property is deprecated in favor of the value property

  • user picker

    • setValue the available argument types are string and null, values represent account ID

    • getValue the properties displayName and avatarUrls are deprecated and will be removed

  • multiple user picker

    • setValue the available argument type is string[], values represent a list of account IDs

    • getValue the properties displayName and avatarUrls are deprecated and will be removed

27 March 2023

Fixed Data residency migration payload updates for the /schedule and /start endpoints to match the specification

The payload for the /schedule and /start endpoints has been updated to match the https://developer.atlassian.com/cloud/jira/platform/data-residency-migrations/ specifications.

 

The /schedule endpoint had an issue where instead of the startTime and endTime fields, the payload contained the windowStartTime and windowEndTime fields, this has now been fixed and the payload contains the startTime and endTime fields.

 

Both the /schedule and /start endpoints were incorrectly sending the location field as lower case, this has now been updated and the location will be provided as uppercase.

24 March 2023

Announcement Custom field and custom field type modules enter GA

We're happy to announce that the custom field and custom field type modules are leaving the Early access program and are becoming generally available. Both modules are ready for production use and we're committed to maintaining them in the current state. We also won’t release any changes that would break backward compatibility without at least six months' notice.

21 March 2023

Announcement Advanced notice to update Atlassian Connect Spring Boot based apps to Java 17

This is an advanced notice that Atlassian Connect Spring Boot (ACSB) will be updated to Spring Boot 3.x which requires Java 17. If you have an app based on ACSB, it is advised to start upgrading to Java 17 now.

More details

Currently Atlassian Connect Spring Boot version 3.0.x is built with Spring Boot version 2.7.6. The 2.7.x version of Spring Boot will be end of lifed (EOLd) by November 18th 2023. Prior to this date a release of Atlassian Connect Spring Boot will be made available which will be built against Spring Boot 3.x. By September 18th we will publish a release of Atlassian Connect Spring Boot, which will be built against Spring Boot 3.x. A deprecation notice will be posted in advance to advise on this.

There are some important dependencies which flow from this change, which your app will need to consider. We suggest you read the announcement at https://spring.io/blog/2022/05/24/preparing-for-spring-boot-3-0

Foremost among these changes will the requirement to build your app with Java 17. This is something you can start working on now, even while using the current version of ACSB and Spring Boot.

17 March 2023

Announcement Data residency UI customer beta is coming soon

From March 29, 2023 we will be introducing a new UI for app data residency which will display app data residency options on admin.atlassian.com. This functionality will be tagged with a ‘beta’ label.

For more information about how to support data residency in Connect, refer to our developer documentation regarding data residency and realm migrations.

15 March 2023

Added New details in the "Storing user personal data for your apps" of the user privacy guides

The Store personal data in locations with restricted access and Use a location with permanent access paragraphs have been added to provide additional clarifications about the requirements when storing user personal data.

These have been added to the Jira https://developer.atlassian.com/cloud/jira/platform/user-privacy-developer-guide/#storing-user-personal-data-for-your-apps and Confluence https://developer.atlassian.com/cloud/confluence/user-privacy-developer-guide/#storing-user-personal-data-for-your-apps guides.

13 March 2023

Removed We're removing deprecated Jira Cloud download attachment and thumbnail URLs

Legacy Jira download attachment and thumbnail APIs will be removed. Please migrate to the corresponding APIs.

This may impact the ability to download attachments from email notifications sent before the transition period.

More details

This change is related to https://community.developer.atlassian.com/t/updated-uris-for-avatars-attachments-and-attachment-thumbnails/53483. The deprecation notice for this was posted four months ago: https://community.developer.atlassian.com/t/deprecation-of-obsolete-jira-cloud-download-attachment-and-thumbnail-urls/63171.

Existing email attachments will reference the legacy API endpoints and may break once these have been removed. Customers are encouraged to download their attachments in advance or navigate directly to the relevant issue to download them.

The migration details are:

Functionality

Deprecated endpoint

New endpoint

Get attachment content - Jira

/secure/attachment/{attachmentId}/{attachmentName}

https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-attachments/#api-rest-api-3-attachment-content-id-get

/rest/api/{v:2|3|latest}/attachment/content/{attachmentId}

Get attachment content - JSM

/servicedesk/customershim/secure/attachment/{attachmentId}/{attachmentName}

https://developer.atlassian.com/cloud/jira/service-desk/rest/api-group-request/#api-rest-servicedeskapi-request-issueidorkey-attachment-attachmentid-get

/rest/servicedeskapi/request/{issueIdOrKey}/attachment/{attachmentId}

Get thumbnail content - Jira

/secure/thumbnail/{thumbnailId}/{thumbnailName}

https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-attachments/#api-rest-api-3-attachment-thumbnail-id-get

/rest/api/{v:2|3|latest}/attachment/thumbnail/{thumbnailId}

Get thumbnail content - JSM

/servicedesk/customershim/secure/thumbnail/{thumbnailId}/{thumbnailName}

https://developer.atlassian.com/cloud/jira/service-desk/rest/api-group-request/#api-rest-servicedeskapi-request-issueidorkey-attachment-attachmentid-thumbnail-get

/rest/servicedeskapi/request/{issueIdOrKey}/attachment/{thumbnailId}/thumbnail

6 March 2023

Announcement Replacement of glances API with expandable API in Jira’s new issue view

In the coming days, we’ll be replacing the Jira issue glance module with a new Jira issue context module. This will improve the way apps are displayed in Jira’s new issue view.

The new extension point will be available at the end of March. We recommend watching the Jira changelog on developer.atlassian.com for the official release of the new API (the Issue context module) and the deprecation of the old API.

In the iOS and Android apps, the new module will be available by default. To prevent your app from appearing on mobile, set the jiraNativeAppsEnabled flag to False.

28 February 2023

Added UI modifications now support new methods in Field API

UI modifications is a Forge module that enables apps to modify fields on the Global issue create modal. It now allows you to use two new Field API methods, setRequired and isRequired. They make it possible to, respectively, set a field as required and check whether a field is set as required.

27 February 2023

Removed Jira xlarge modal will experience a behavioural change from today, Feb 27, 2023

In Jira, the Custom UI modal class size argument with xlarge value with 100% width is replaced with 998px from today, Feb 27, 2023, AEST.

For more information on this deprecation notice, see https://developer.atlassian.com/platform/forge/changelog/#CHANGE-816.

Added Information about user that triggered the webhook for non-Connect webhooks in Jira

Starting today, the triggeredByUser query parameter containing the account ID of the user that triggered the webhook will be added to all webhooks. The following exceptions apply:

  • the account ID is unavailable,

  • the event is user-related,

  • the webhook originates from a Connect module.

20 February 2023

Announcement Reminder: Starting February 27th, 2023, there will be a behavioural change to the Jira xlarge modal size

In Jira, the Custom UI modal class size argument with xlarge value with 100% width will be replaced with 998px.

For more information on this deprecation notice, see https://developer.atlassian.com/platform/forge/changelog/#CHANGE-816.

Fixed Lowered Connect scope required to access the bulk get groups API

In response to a JRACLOUD suggestion, we’ve lowered the Connect scope required to access the /rest/api/*/group/bulk API. Starting from now, the READ scope is sufficient to perform calls to this API.

15 February 2023

Added IssueType will support hierarchy levels ≥ 1

The value of the hierarchyLevel property of issuetype will be its level in Hierarchy Configuration. For example, an issue type at level 2 in the issue type hierarchy will now have a hierarchyLevel of 2.

This change will be released after Apr 1, 2023. It will affect all API endpoints that return issuetype as part of the issue fields.

More details

Previously, hierarchyLevel was 0 for issue types at levels ≥ 1 in Hierarchy Configuration. Only the system Epic issue type had hierarchyLevel 1.

There will be no change in hierarchyLevel for base-level issue types (0) and subtasks (-1).