Last updated Mar 1, 2024


This changelog is the source of truth for all changes to the Forge platform that affect people developing Forge apps.

Posts are made in the Forge announcements category of the developer community when the changelog is updated. Subscribe to the Forge announcements category to get notifications.

See what's next for Forge on our platform roadmap.

1 March 2024

Early Access New custom merge check trigger for reviewer status changes

We added a new on-reviewer-status-changed trigger type for Bitbucket Custom Merge Checks (currently available under EAP). You can use this trigger type to invoke your check whenever a reviewer status changes. See the Custom merge check (EAP) - Triggers page for details.

29 February 2024

Announcement Action required to avoid performance impacts and to offer data residency for Forge hosted storage apps in beta

From the end of March, 2024, Forge hosted storage will start to include data residency by default.

With data residency available for Forge hosted storage, you have an efficient new option to meet customer data residency needs with minimal additional investment. Forge will take care of the hosting, pinning, and migration of data stored in Forge hosted storage, so you can focus on building a high quality app for your customers.

To prepare for this change, there are a few steps you’ll need to take for all Forge apps, especially those that use Forge hosted storage:

  1. By Mar 28, 2024:

    1. If you have no remotes or external permissions defined for your app, no manifest changes are required, but we recommend you redeploy to get the benefits of multi region compute.

    2. If you have remotes or external permissions defined for your app you will need to provide more information for each remote in your manifest. This will ensure customers see that your apps will move and be pinned with the host product in For instructions, read here.

  2. By Mar 28, 2024: redeploy your app, regardless of whether you’ve made updates to your manifest — this will allow your app to benefit from multi-region compute and maintain performance when pinned. Failure to redeploy by late March could result in performance impacts for some customers.

Customers will need to be on the latest major version of your app to benefit from multi-region compute and avoid potential performance impacts. We will communicate with customers to encourage them to upgrade in early April.

Learn how to do this here.

More details

Data residency for Forge hosted storage is the latest milestone on our shared mission to offer enterprise-ready apps to customers in cloud. With data residency available for Forge hosted storage, meeting a key customer trust requirement will be easier than ever.

Just store any in-scope data (data that’s in-scope for data residency) in Forge, update your manifest to let Atlassian know, and update your Privacy & Security tab to let customers know about your app’s support for data residency starting in April.

It’s important to note that, as we shared here last November, when data residency reaches Beta for Forge hosted storage, app data stored in Forge hosted storage will automatically inherit data residency in all current and future regions supported by the host product. This will not be reversible.

You can read more details about data residency for Forge hosted storage here.

Announcement Forge hosted storage platform migration is resuming

Rollout: progressive rollout by app and environment. in progress

Migration to the new backing platform for Forge hosted storage is resuming starting 2024-03-01 00:00 UTC.

The remaining apps will be migrated progressively with expected completion by 2024-03-22 00:00 UTC at the latest. This progression will be across both app and environment as it maps to how the data is partitioned in hosted storage.

Please note that as the app and the environment are onboarded, the query cursor format will change. To support a smooth transition, we will support the old format for a short amount of time post cut-off.

Please check the scheduled maintenance report on Statuspage for more details about the cursor change and receive updates as we progress through the rollout.

Early Access Confluence Cloud Embeds EAP

Summary of EAP:

We are planning to launch Confluence Embeds to our customers. At the end of March 2024, we’ll be integrating Embeds as a new content type within Confluence that will exist within the current navigation and creation structures, including the content tree. Users would be able to add an embedded view of a smart link directly from the Create buttons and in the content tree.

Apps that directly use content tree (fka page tree) in their functionality maybe at risk. We would highly urge those app developers to proactively test when the changes are available through DCP in your test tenants.

As we prepare to go live with the upcoming changes, we would like to seek your collaboration in validating and mitigating any potential impact that these changes may have on your applications.

  • To facilitate this process, all required changes will be available through this EAP.

    Join the EAP by raising a ticket here:
    This will allow you to thoroughly test your applications and report back any impact or issues that you may encounter. We will provide updates to EAP tickets once the requested tenants have joined the EAP.

If your application is impacted by the changes, please comment in the EAP community. We are looking forward to working together with you to resolve any issues before releasing the new content type to our shared customers.

Reiterating, this change is very similar to those made when introducing Whiteboards and Databases, so it should be similar to validate. We highly urge you to make your apps generic enough to accept any new content types in the future to avoid any disruption.

More details


The fundamental user problem that we are trying to solve - “Teams' success depends on easily finding and accessing the right information needed to do their work.”

We have a strong belief that users desire a unified platform for all their content across various applications, and Confluence is an absolute right fit to be that connected workspace for users and their team.


To solve the above problem, we are introducing Embeds as a new content type. Basically any user can add an embedded view of a Smart Link in the content tree. This can be an existing confluence page, a loom recording, a google sheet, figma file, etc.

This would exist as a native content type within Confluence, with functionality and behaviors similar to other existing content types. These include but are not limited to existing in the tree, and being able to be created from the create button.

We will provide important details about this upcoming change and what you need to know as an ecosystem developer.

What is changing in the upcoming release?

In one of the upcoming releases, Embeds will be added to Confluence’s current navigation structure.

Important Note: The changes are very similar to those associated with the introduction of Whiteboards & Databases to Confluence, so it shouldn’t bring any new surprise. ( previous RFCs on Whiteboards RFC-10: Confluence Whiteboards and Databases RFC-23: Confluence Databases ).

Here are the most relevant upcoming changes:

Embeds Creation

  • Embeds can be created similarly to pages’ creation mechanism

  • Embeds can be created both through the top navigation ‘Create’ button and clicking on “Smart Link”

  • Embeds can be created through the “+” button next to Content in the sidebar.




Embeds in the Content Tree

  • Embeds will co-exist in the content tree with other content types such as Pages Whiteboards and Databases. They will be able to be parent nodes as well as child nodes

  • Content actions including Rename, Copy Link, Copy, Move Archive, and Delete will be available for Embeds


When will this change take place?

The feature will be released to customers in a measured rollout process starting at the end of March 2024 to be completed over 4-5 weeks. Enterprise customers would be able to control the availability of the feature through Release tracks.

How might this affect you?

With the upcoming changes, some of our APIs will be updated to include Embeds-related information in the response. Examples of such APIs are:

  1. Rest APIs

    1. Endpoints that return children/descendants and ancestors for a Content that support the following expand parameters will be affected. E.g.

      1. ancestors  - will now return Embeds in the response.

      2. childTypes.all - this will not be affected immediately but will include Embeds in the future.

    2. Endpoints under Content - children and descendants will not be affected immediately but we will include Embeds in the response.








      c. Content body expand will be empty for Embeds /wiki/rest/api/content/{id}/

  2. GraphQL APIs
    i. ConfluencePage.ancestor


Note: Support for v2 CRUD APIs for embeds will be available soon!

26 February 2024

Announcement Create and edit with greater context and control

We are rolling out an update to Confluence’s page creation & editing experience. The Confluence sidebar (content tree) and top navigation will now be visible while editing to make it easier for users to understand where they’re creating, and reduce the degree of context switching between editing and viewing pages. This is currently rolled out to a portion of customer sites, and is continuing to roll out to all customers over the next week.
There are a couple of newly possible cases with Extension points we’d like to highlight:

  • By displaying the space sidebar while editing, it’s now possible for a Confluence user to see and interact with Space Sidebar Web Items while in the editing experience.

  • Furthermore, web items available in the editing experience - the Edit Page Precursor Web Item, Editor Save Bar Panel, and web-panels associated with atl.general - are slightly shifted due to the updated toolbar experience & presence of an expanded or collapsed sidebar next to the editor.

More details

Note: This feature is not the same as as the “Live-Edit Pages EAP” that has been previously mentioned in the changelog. This feature applies to the editing experience for both standard published pages and Live-Edit Pages. Live-Edit pages are only available to a small set of early access customers and vendors that have chosen to opt in.
Learn more in our community post here.

22 February 2024

Announcement Data security policy events documentation now published

To prepare your apps for the upcoming General Availability of app access rule functionality, we’ve published documentation on new data security policy events. Customer release is scheduled for the end of Q1 of the calendar year 2024.

The new events will be available for early access by developers in late February, 2024. We’ve published this documentation in advanced so you can start preparing your apps to receive the event notifications when appropriate.

More details

We have updated the following guides with information about the new data security policy events your app can subscribe to:

Additionally, a new reference page has been added for Forge app developers.

Announcement UI modifications support new fields

The UI modifications (UIM) module now supports new fields on the issue view:

The complete list of supported fields for the issue view is here.

21 February 2024

Early Access Export of app logs to observability tools

You can now use the App logs API, as part of an early access program (EAP) to export Forge app logs to third-party observability tools of your choice. See App observability in third-party tools and Export app logs for details.

You can use this sign-up form to join the program.

19 February 2024

Added Jira Data Classification REST APIs

We’ve added 4 new APIs that enable you to get, update, and delete the default classification level on a project, as well as to get the list of all classification levels.

15 February 2024

Announcement Improvements to Forge app logs (preview)

Rollout: progressive rollout by app. in progress

As part of the ongoing preview release, we’re now making it easier for apps to get the new Logs experience available on the developer console. This will be a progressive rollout so the changes may not be immediately available for your Forge apps.

The new experience provides capabilities that further refine log results, including using new filters, such as log levels, and searching for log messages.

To get the new experience for your app, we recommend doing one or both of the following:

  • Make sure your app is on the latest version of Forge runtime by running forge deploy for a minor version upgrade.

  • Encourage your users to upgrade to the latest version of your app. Site admins may need to provide consent if a major version upgrade of their app is required.

Fixed Reverted returned value for last page of cursor results in Query API

Previous versions of the Query API returned an undefined response for the cursor value on the last page of results. In a recent update, we changed the response to an empty string, which caused unexpected errors in some apps.

To avoid these errors, we reverted this specific change.

For more information, see

13 February 2024

Early Access Live-Edit Pages EAP

For more details, please see our RFC.

To make page creation & collaborative editing easier, we are in the early stages of testing Live-Edit Pages with customers. Live-Edit Pages are continuously editable for users with editing permissions, without any additional clicks to enter or exit the editing mode.

We want to be clear, this EAP is very early testing, and is not representative of a final feature. We plan to make many changes along the way that incorporate feedback and what we’ve learned before each stage of rollout. We are particularly keen to get your feedback other potential impacts of Live-Edit Pages on apps we may have missed as well as how we can best support your apps in Live-Edit Pages, so we can add them to our roadmap during the EAP and beyond.

To participate, please:

  1. Read our RFC here for more details, and leave any feedback you have

  2. Sign up for the Partner Early Access Program here.

More details

The documentation for this EAP is available at

8 February 2024

Deprecation Notice Deprecation of form-encoded and uri-query bearer methods

We are deprecating the form-encoded and uri-query bearer methods for external authentication due to lack of use in apps. These methods will not be included in the new native Node.js runtime. In addition, deployments to the current runtime will no longer be able to use these bearer methods after May 9, 2024.

If you plan to integrate with an API that uses form-encoded or uri-query but doesn't support the authorization-header bearer method, please let us know on our public feedback board.

6 February 2024

Announcement App access rule under data security policies: early access for Jira customers and partners live this week

This week, select customers will be given early access to the app access rule for Jira Cloud. Customers will be asked to test the functionality, and warned that app functionality will be impacted when apps are blocked from accessing projects.

Marketplace Partners in the app access rule EAP have had access to this feature in Confluence since November 2023. Early access participants will now be given access to the feature in Jira and to the Jira app access rule API. This will allow you to prepare your apps for any potential end user impacts when the app is blocked by an app access rule.

More details

Data security policies help customers keep their organization’s data secure by letting them govern how users, apps, and people outside of their organization can interact with content such as Confluence pages and Jira issues.

The new app access rule under data security policies allows customers to restrict access for all apps to the Confluence spaces or Jira projects under a given policy. This should make it easier for customers with more strict data privacy concerns to install your apps while maintaining control over access to certain content.

If you’d like to participate in the developer EAP for this feature, which gives you access to the app access rule and new app access rule API to test, sign up here.

5 February 2024

Announcement UIM support for new methods for multiple Issue view fields

The UI modifications (UIM) module now supports the getDescription() and setDescription() methods for the following fields on the Issue view:

All the supported methods and fields can be found here.

Rate this page: