Last updated May 24, 2024

Atlassian developer changelog

This page contains announcements and updates for developers from various products, platforms, and programs across Atlassian. It includes filter controls to make it easier to only see updates relevant to you.

To ensure you don’t miss any updates, we also provide RSS feeds. These feeds will take on any filters you applied to the page, and are a standardized way of keeping up-to-date with Atlassian changes for developers. For example, in Slack with the RSS app installed, you can type /feed <FEED URL> in any channel, and RSS updates will appear in that channel as they are posted.

24 May 2024

Deprecation Notice Type of the `id` field for some entities in Confluence webhooks changed from `number` to `string`

Connect - Confluence Cloud (excludes Confluence REST APIs)

As we announced in this community post, we’ve now changed the type of the id field for page, blogpost, attachment, and comment entities in Confluence Webhooks to be string instead of number. If your app switched to idAsString field after the previous announcement, please switch it back to using id field.

This change doesn’t affect id field of space entities.

idAsString field is now deprecated and will be removed from Confluence Webhooks in 6 months.

More details

Full list of affected webhooks:

  • attachment_archived

  • attachment_created

  • attachment_removed

  • attachment_restored

  • attachment_trashed

  • attachment_unarchived

  • attachment_updated

  • attachment_viewed

  • blog_created

  • blog_removed

  • blog_restored

  • blog_trashed

  • blog_updated

  • blog_viewed

  • comment_created

  • comment_removed

  • comment_updated

  • content_permissions_updated

  • label_added

  • label_created

  • label_deleted

  • label_removed

  • page_archived

  • page_children_reordered

  • page_created

  • page_copied

  • page_moved

  • page_removed

  • page_restored

  • page_trashed

  • page_unarchived

  • page_updated

  • page_viewed

  • space_created

  • space_logo_updated

  • space_permissions_updated

  • space_removed

  • space_updated

23 May 2024

Announcement The public migration API is now available for all

Migration API

We’ve completed the beta phase for the migration API and are now moving it to general availability (GA).

As a part of the GA release, we’re also adding the following features for jira-onpremises-to-cloud jobs (JCMA >= 1.11.4):

  1. Support for archived issues. They will now be migrated by default. If you wish to skip migrating archived issues, you can use the includeArchivedIssues=false flag in projects.

  2. Support for dashboards. Jobs will now migrate all dashboards by default. If you don’t wish to migrate dashboards, you can set the dashboards mode to NONE.

  3. Support for migrating boards and filters with the following options (read more here link):

    1. ALL - This includes all filters (both single and cross-project) and cross-project boards, irrespective of their shared access.

    2. SCOPED - (Default) Only migrate boards and filters shared with selected projects. This includes both single and cross-project boards and filters that have been shared with the projects selected for migration.

    3. NONE - Doesn’t migrate boards and filters.

  4. Support for progress details in the status API (link).

For more details about the API’s functionality, go to

22 May 2024

Deprecation Notice Deprecation of search priorities API 'onlyDefault' parameter and 'isDefault' property

REST API - Jira Cloud Platform

We are deprecating the following functionality of the Search priorities REST API endpoint.

  • The onlyDefault parameter is deprecated and will be removed at a later date.

    • Users are instead encouraged to use the recently announced Get priority scheme, which includes the ID of the default priority, and optionally a list of associated priorities.

  • The isDefault property of priorities is deprecated and will be removed at a later date.

More details
  • The onlyDefault parameter is deprecated and will be removed at a later date.

    • Users are instead encouraged to use the recently announced Get priority scheme, which includes the ID of the default priority and, optionally, a list of associated priorities.

    • During the transition, this will return the global default priority and may not be the default priority for any priority scheme.

  • The isDefault property of priorities is deprecated and will be removed later.

    • Users are instead encouraged to use the recently announced Get Priorities by Priority Scheme endpoint, which lists priorities and includes whether they are the default for the priority scheme.

    • During the transition, this will return true for the global default priority only and may not reflect whether a priority is a default for any priority scheme.

Announcement Multi-Bodied Macro Extensibility GA

Connect - Confluence Cloud (excludes Confluence REST APIs)

We are pleased to announce the GA of our Multi-Bodied Macro feature for Confluence Cloud, following the valuable feedback received during our EAP. This feature allows app developers to create dynamic content macros with multiple bodies. App developers can manipulate macro bodies – adding, deleting, or setting an active body for users to view. This functionality is designed to enhance content flexibility and interactivity on Confluence pages. For implementation details, please refer to the macro module documentation and tutorial.

A special thank you to all participants who engaged with us through the EAP and provided insightful feedback and suggestions on our RFC.

We encourage everyone to explore the new capabilities of the Multi-Bodied Macro, now fully available for use.

21 May 2024

Announcement Export of app logs now generally available

Forge - Core Platform (excludes product REST APIs)

Following its early access release, the ability to export app logs to third-party tools via the App Logs API is now generally available. See App observability in third-party tools and Export app logs for details.

Send us any feedback you may have via the “Give feedback” button in the “Get help section” at the top right-hand side of the developer console.

Added Improvements to outbound OAuth 2.0 on Forge

Forge - Core Platform (excludes product REST APIs)

We have made a number of improvements to Forge’s outbound OAuth 2.0 capabilities that give you more flexibility around scopes and accounts.

You can now:

  • Allow users to connect multiple accounts to the same provider. You can retrieve a list of the accounts that a user has connected and specify which account to use when calling withProvider().

  • Retrieve the account information for a user’s connection including which scopes they have granted.

  • Specify which scopes to request during a requestCredentials() call.

  • Specify required scopes for an OAuth 2.0 provider at a function level. If the user hasn’t already authorized the scopes for that provider they will be taken to the consent flow when the function is invoked.

  • Make requestCredentials() calls without triggering invocation errors in the Forge metrics ( ).

20 May 2024

Announcement The preview API for improved distributions data is now accessible

Marketplace Platform

We are excited to announce the release of the preview API for improved distributions data for our partners!

As announced earlier, we have been working on enhancing distributions (active installation and user counts) data. We have made improvements to the way we provide and calculate the distributions (installation and user counts) for various aggregations. Along with that, we have also reduced the latency of retrieving this data from one week to one day.

Due to these adjustments in logic and latency, we intend to grant partners access to the data through a preview API by using /vendors/{vendorId}/partner-metrics-preview.

For more details on the changes in logic and how to access the data, you can read the quick reference guide and documentation. It's important to be aware that historical data will not be included in this preview API release but will be incorporated during the final rollout in June. Additionally, there might be variations in the data retrieved by partner metrics API and the existing REST APIs due to changes in logic.

We are currently aiming to make the enhanced distribution counts generally available to our partners around June 2024. From then on, partners will be able to use the partner metrics API as well as the existing APIs for distributions to get the improved count. In case of any queries, partners can reach out to us by commenting on the referenece guide linked above to get more information.

Added Audit logs for apps using Forge-hosted storage

Forge - Core Platform (excludes product REST APIs)

As part of the data residency rollout, app admins can now download audit logs for Forge apps that use hosted storage. Audit logs contain details for audit events related to changes made in the storage location of app data. App admins can access audit logs via the developer console.

See Download audit logs for more information.

17 May 2024

Announcement Introducing Data Center security checklist and best practices

Bamboo Data Center
Bitbucket Data Center
Confluence Data Center
Crowd Data Center
Jira Data Center
Jira Service Management Data Center

We're introducing a Data Center security checklist and best practices for admins. This guide will provide you with valuable insights on safely deploying and administering Atlassian self-managed software.

More details

We value your input and actively encourage feedback from the community. Your contributions will help us refine this guideline into the most reliable source of information for admins. Please select the "Provide feedback about this article" link located at the bottom of the document.

16 May 2024

Deprecation Notice Loading styles from Connect CDN instead of inline

Connect - Core Platform (excludes product REST APIs)

We're deprecating injecting stylesheets for Connect apps via inline styles in favor of loading from the Connect CDN. This affects the Theming API and dynamic content macros that supported the legacy Confluence editor.

At the end of the deprecation period (18th November 2024), we’ll stop injecting any inline styles and only load from the CDN.

If your app doesn’t use the above Connect features, or doesn’t use a Content Security Policy (CSP) for style-src, no action is required. Otherwise, please read the details here or see on how to modify your CSP to support these changes.

More details

Action required

To support these changes in your app, if you're using a Content Security Policy that sets the style-src policy, you must add the Connect CDN ( to your policy to allow these stylesheets to be injected. It's safe to remove unsafe-inline from your policy if you've been using it up until now.

Additional context

The stylesheets mentioned here are included automatically via the Connect JS script, not manually by the app vendor. There are two circumstances under which Connect injects stylesheets into your app.

The first is only for apps which opted in to the Theming API. The theme stylesheets currently load via an inline stylesheet, which forces vendors to adopt the insecure unsafe-inline policy, and is the main motivation for this change.

The second location is only for dynamic content macros. We inject a stylesheet with CSS classes representing colors from the legacy Confluence editor. This happens without opt-in, to be backwards-compatible with macros created in the legacy editor. This injection is currently done via CSSOM, not inline styles, and therefore isn’t impacted by style-src CSP rules currently. However it’ll also start being served from the CDN.

During the deprecation period, styles will be loaded simultaneously via the current methods described above and from the CDN. After the deprecation period, styles will only be loaded from the CDN, and the inline/CSSOM methods will be removed.

15 May 2024

Added requestBitbucket is now available in @forge/bridge

Forge - Bitbucket (excludes Bitbucket REST APIs)
REST API - Bitbucket Cloud
  1. requestBitbucket is now available in @forge/bridge, so you can make Bitbucket API fetch requests from the front end of a UI Kit or custom UI app. For more information on using requestBitbucket, see the Part 2: Call a Bitbucket API tutorial.

Early Access Two-step verification in Jira Software and Jira Service Management

Jira Data Center
Jira Service Management Data Center

This change is still a work in progress.

We’re working on improving the security of our login experience for Jira Software and Jira Service Management by allowing customers to add a native second authentication layer.

The new login process will support a built-in two-step verification (2SV) capability managed by the Atlassian SSO for Data Center app implemented as a system plugin using a time-based one-time password (TOTP) as a second factor.

This change is scheduled to be included in a future feature version following the initial release of Jira Software 10.0 and Jira Service Management 6.0. Today, we’re happy to announce that we’re launching an Early Access Program (EAP) to seek feedback for the prototype of this solution and invite you to take part in this. Follow the Atlassian developer changelog for updates.

Request for Comments (RFC) RFC: Multiple Help Centers on Jira Service Management

Connect - JSM Cloud (excludes JSM REST APIs)
Forge - JSM Cloud (excludes JSM REST APIs)

14 May 2024

Deprecation Notice Changes to Assets /object/aql and /object/navlist/aql endpoints


We are making changes to the /object/aql and /object/navlist/aql endpoints within the REST API’s for Assets in Jira Service Management cloud.

  • We will be removing the total attribute from the response payload of the /object/aql endpoint. If you require this, instead use the /object/aql/totalcount endpoint which will provide a total count for any AQL query.

  • We will be removing /object/navlist/aql from our list of supported public endpoints and it should now be considered deprecated. Instead we recommend you migrate to the /object/aql endpoint.

These changes will be made on or after 30 Sept 2024.

Announcement New API endpoints to fetch, create, update, and delete priority schemes

REST API - Jira Cloud Platform

We’re happy to inform you that we’re making the following new API endpoints available:

  • Get priority schemes

    • Returns a paginated list of priority schemes

    • GET /rest/api/3/priorityscheme

  • Get available priorities by priority scheme

    • Returns a paginated list of available priorities to be added to a scheme

    • GET /rest/api/3/priorityscheme/priorities/available

  • Get priorities by priority scheme

    • Returns a paginated list of priorities

    • GET /rest/api/3/priorityscheme/{schemeId}/priorities

  • Get projects by priority scheme

    • Returns a paginated list of projects

    • GET /rest/api/3/priorityscheme/{schemeId}/projects

  • Create priority scheme

    • POST /rest/api/3/priorityscheme

  • Update priority scheme

    • PUT /rest/api/3/priorityscheme/{schemeId}

  • Delete priority scheme

    • DEL /rest/api/3/priorityscheme/{schemeId}

  • Suggested priorities for mappings

    • Returns a paginated list of priorities

    • POST /rest/api/3/priorityscheme/mappings

Rate this page: