Last updated Mar 31, 2025

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.

31 March 2025

Announcement fiveMinute scheduled trigger interval is now GA

Forge - Core Platform (excludes product REST APIs)

The fiveMinute scheduled trigger interval is now generally available (GA).

Developers can now use the scheduled trigger module to create scheduled trigger modules in a Forge app with intervals of fiveMinute, hour, day, and week.

For more information on using these intervals, see the https://developer.atlassian.com/platform/forge/manifest-reference/modules/scheduled-trigger/#scheduled-trigger module documentation.

Added New openOnInsert parameter for Forge macro custom configuration

Forge - Confluence Cloud (excludes Confluence REST APIs)

We’ve added a new optional parameter openOnInsert to the configuration object in the manifest of Forge macros. This allows developers to control if the custom configuration modal is automatically opened when first inserted.

For more information, see Macro.

Added New fields for Update custom content REST API V2 endpoint

REST API - Confluence Cloud

We have added support for the following request body fields for the Update custom content REST API V2 endpoint:

  • spaceId

  • pageId

  • blogPostId

  • customContentId

29 March 2025

Announcement Text and Heading UI Kit components have been updated

Forge - Bitbucket (excludes Bitbucket REST APIs)
Forge - Compass
Forge - Jira Cloud Platform (excludes Jira REST APIs)
Forge - JSM Cloud (excludes JSM REST APIs)
Forge - Jira Software Cloud (excludes JSW REST APIs)
Forge - Confluence Cloud (excludes Confluence REST APIs)

We have updated our UI Kit components, Text and Heading to make them more flexible:

Text

  • Now supports align, as, color, maxLines, size and weight properties.

For more information, see Text component documentation.

Heading

  • You can now control how the Heading component appears by setting a value for size, while the as prop controls the HTML element's rendering.

For more information, see Heading component documentation.

27 March 2025

Announcement Introducing Verified Trust Center Links for Enhanced Marketplace Trust

Marketplace Platform

We're excited to announce a new, live feature that allows Marketplace Partners to display verified third-party trust center links on their app listings and partner profiles. This initiative aims to enhance transparency and build trust by giving customers easy access to verified compliance and security information.

Adding this link is optional but as part of the recent updates to the Marketplace Partner Program, it will become mandatory for Platinum partners to include links to a third-party verified trust center starting in July 2025.

26 March 2025

Added Support for macro autoconvert in Forge UI Kit

Adopting Forge from Connect
Forge - Confluence Cloud (excludes Confluence REST APIs)

We are happy to announce we have added support for macro autoconvert to UI Kit. This allows your app to automatically insert a macro into the editor when a user pastes a recognized URL.

For more details, please see the Macro documentation.

More details

This feature provides equivalent Forge functionality to macro autoconvert with Confluence Connect.

25 March 2025

Deprecation Notice Third reminder: Deprecating a subset of Confluence page extension points

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

Reminder: Starting Apr 30, 2025, a subset of Connect extension points will no longer be available on Confluence pages. For details, see the original deprecation notice linked below.

deprecation notice Deprecating a subset of Confluence page extension points

Action is required from developers using deprecated extension points.

Announcement UI Kit component documentation now accessible via JSDoc

Forge - Core Platform (excludes product REST APIs)

We are pleased to announce that UI Kit component reference documentation is now embedded within the component source using JSDoc.

This enables developers to access component information directly from their integrated development environments (IDEs), improving the development workflow.

This is available for developers using @forge/react@11.1.0 or above.

More details

To update to the latest version of @forge/react, in the terminal from your project directory, run the following command:

npm install --save @forge/react@latest

Announcement Update minimum required Node.js version for Forge CLI

Forge - Core Platform (excludes product REST APIs)

The minimum compatible Node.js version for the Forge CLI has been updated to 18.20.7. Developers running older versions of Node.js will need to upgrade to this version or later to continue using the Forge CLI. This change ensures that all developers have access to the latest features, security updates, and performance improvements.

More details

We recommend that you upgrade the Node.js version to 20 or 22, as Node.js 18 will reach end-of-life soon.

Announcement Sale Type Improvements for Transactions Report

Marketplace Platform

Marketplace is updating the logic for calculating the saleType provided via the transactions report.

To determine the sale type within transactions, we currently rely solely on the difference in user count from previous transactions.

With the upcoming improvements to the sale type:

  • The type of sale will be defined by the interplay between the gross list price and the editions offered. The gross list price represents the total amount a customer must pay based on the listed price, without accounting for any deductions or adjustments. This approach shifts our focus away from fluctuations in user count to a more inclusive logic. Changes in either of these factors will influence the sale type, with greater emphasis placed on the gross list price. For instance, the gross list price goes up while the customer downgrades their edition. The sale type will consider both these factors and with a higher emphasis on change in gross list price, the sale type will be UPGRADE.

  • We are introducing a new sale type referred to as DOWNGRADE. If there is a reduction in the gross list price compared to previous transactions, or if the edition is downgraded while the gross list price remains unchanged, the transaction will be classified as a downgrade.

  • The same will be reflected in the user experience for partner reporting

We encourage our partners to gain a comprehensive understanding of the new logic. For more details, refer to the quick reference guide.

Request for Comments (RFC) Role-based access control in Confluence - Roles API & the access Apps can set with it

REST API - Confluence Cloud

The project addresses the integration of role-based access control (RBAC) in Confluence, focusing on its impact on apps and the ecosystem. The proposal suggests restricting apps from creating, updating, or deleting custom roles to prevent issues related to role limits per site. We are seeking feedback to determine if apps can continue updating user access using default roles and whether product admins should configure roles for apps to use.

https://community.developer.atlassian.com/t/rfc-91-role-based-access-control-in-confluence-roles-api-the-access-apps-can-set-with-it/90673

24 March 2025

Deprecation Notice Forge Invocation Tokens (FIT) 'app.version' field

Forge - Core Platform (excludes product REST APIs)

The app.version property in FIT contains a string used by some internal Atlassian services. As such, it does not accurately represent the actual app version. To refer to the correct Forge app version, use the new app.appVersion property instead.

The app.version property will be removed on Sep 25, 2025.

Added New component property for CustomFieldEdit

Forge - Core Platform (excludes product REST APIs)
Forge - Jira Cloud Platform (excludes Jira REST APIs)
Forge - JSM Cloud (excludes JSM REST APIs)
Forge - Jira Software Cloud (excludes JSW REST APIs)

In the latest version of @forge/react, we're adding a new disableSubmitOnBlur property to the UI Kit Jira component, CustomFieldEdit. The property can be used to disable the submission of the field value on blur events.

For more information on this component, see the component documentation.

More details

To update your UI kit app to the latest version, run the following command in your project directory:

npm install --save @forge/react@latest

Added New APIs for fetching children/descendants

REST API - Confluence Cloud

We’ve added V2 API endpoints to retrieve children and descendants for pages, databases, smart links, whiteboards and folders.

To enable these new V2 APIs, you’ll need to use the new Oauth 2.0 scope read:hierarchical-content:confluence.

These new APIs correspond to the following V1 APIs, which have been marked as deprecated (and will be retired on Apr 30, 2025):

More details

Here are the new V2 endpoints:

/pages/{id}/direct-children
/pages/{id}/descendants
/databases/{id}/direct-children
/databases/{id}/descendants
/embeds/{id}/direct-children
/embeds/{id}/descendants

/whiteboards/{id}/direct-children
/whiteboards/{id}/descendants
/folders/{id}/direct-children
/folders/{id}/descendants

21 March 2025

Deprecation Notice Changes to support for uploading marketing assets through app artifact

Marketplace Platform

From Apr 30, 2025, uploading visual marketing assets through app artifacts (.jar, .obr, or .jwb) will no longer be supported. Instead, partners now have the option to use either the UI or the APIs to upload their branding assets, both of which are already available.

You can continue to upload your software using the existing option or the API. However, to upload marketing assets, you must use the publish experience or the API and upload the assets during that process, rather than using the app artifact upload option.

This change is part of the broader Marketplace Technical Foundations initiative.

For any comments or questions, please submit a support request.

More details

After the deprecation period on Apr 30, 2025, you will not be able to use the following options to upload your marketing assets:

UI:

APIs:

To upload your assets, follow these options:

Using UI

  • App logo: Navigate to the About app section, and select Upload logo.

  • Page design assets: Navigate to the Page Design section, select the desired page design type, and click the Add Another Image button to upload your assets.

Using APIs

Rate this page: