Last updated Feb 23, 2024

Confluence Cloud Changelog

This page includes release notes and updates for Confluence Cloud app developers. Use this page to keep track of upcoming changes, deprecation notices, new features, and feature updates from Confluence Cloud.

Forge changelog

For updates about changes to the Forge platform, see the Forge changelog in the Forge documentation.

You can also ask questions and learn from other Confluence Cloud developers on the Atlassian Developer Community.

23 February 2024

Announcement Clarification made to the description of the endpoint PUT /wiki/rest/api/content/{id}/restriction

We've updated the description of the REST API PUT /wiki/rest/api/content/{id}/restriction (described here: https://developer.atlassian.com/cloud/confluence/rest/v1/api-group-content-restrictions/#api-wiki-rest-api-content-id-restriction-put)), as the original description was misleading. The old description was:

Updates restrictions for a piece of content. This removes the existing restrictions and replaces them with the restrictions in the request.

The new description is:

Updates restrictions for a piece of content. For each operation specified in the request, it removes any existing restrictions on the content for that operation, and replaces them with the restrictions in the request.
Note: Not specifying an operation will ignore restrictions of that type, and passing an empty list for an operation will remove all existing restrictions of that type.

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 https://developer.atlassian.com/platform/forge/events-reference/data-security-policy-events/ reference page has been added for Forge app developers.

21 February 2024

Added Adopting Forge from Connect (preview)

We’re pleased to announce the preview availability of adopting Forge from Connect.

Existing Connect apps now have a simpler, automated and incremental pathway to adopt Forge capabilities. This release includes:

  • Automated tooling to support the conversion from Connect to Forge

  • Support for immediate version updates of Forge apps containing connectModules

  • Increased compatibility for the types of connectModules that can be declared within a Forge manifest

  • Support for Forge Remote Compute (preview) in the Atlassian Connect Express (ACE) and Connect Spring Boot (ACSB) frameworks.

20 February 2024

Added New Optional Include Field Parameters for Get Attachment By Id Confluence Cloud v2 REST API

We’ve added a set of new query parameters to the v2 Get attachment by id API that allows for optional fetching of metadata properties related to the given attachment. These include:

  • include-version

  • include-versions

  • include-labels

  • include-operations

  • include-properties

By default, these metadata properties (besides version) will not be included in the response unless specified.

More details

The version property is already included by default in the response, but you can use include-version=false to omit it.

16 February 2024

Announcement Atlassian Connect Express (ACE) version 10.0.0 available

A new version of Atlassian Connect Express (version 10.0.0) has now been published which supports new ngrok configuration options. We recommend upgrading to this version if you are utilising automatic registration in ACE.

Please switch to using the new field ngrok in your credentials.json, as detailed in the README.

15 February 2024

Announcement Atlassian Connect Express (ACE) version 9.0.0 available

A new version of Atlassian Connect Express (version 9.0.0) has now been published which implements @ngrok/ngrok. We recommending upgrading to this version if you are utilising automatic registration in ACE.

Please note that a new field ngrokToken is required in your credentials.json file to support this change, as detailed in the README.

14 February 2024

Added Add editor and styled_view body formats to Page and Blogpost Confluence REST API v2 endpoints

We’ve added support for the styled_view and editor body formats in the Get blog post by id and Get page by id V2 endpoints.

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 https://community.developer.atlassian.com/t/rfc-36-live-edit-pages-in-confluence-cloud/77271.

12 February 2024

Added New Optional Include Field Parameters in the Confluence Cloud v2 REST APIs

We’ve added a set of new query parameters to the v2 Get page by id and Get blog post by id APIs that allow optional fetching of metadata properties related to these resources. These include:

  • include-labels

  • include-properties

  • include-likes

  • include-operations

  • include-versions

  • include-version

By default, these metadata properties (besides version) will not be included in the response unless specified.

More details

The version property is already included by default in the page and blog post responses, but you can use include-version=false to omit it.

Early Access Multi-Bodied Macro Extensibility for Confluence Cloud EAP

We are excited to announce an early access program (EAP) for a new feature that we previously posted about in this RFC.

With this feature, a new macro type will be available in the new editor to enable storage of multiple bodies. App developers can create a new macro by adding a dynamic content macro with the bodyType set to multi-body-rich-text. This macro will be rendered on Confluence pages along with an active body. Within the macro, app developers can create logic to manipulate the bodies of the macro: adding or deleting them, or designating a particular body as the active one that is visible to users. All API functions are available through a new macro module, which is described here.

Please note that the app's capacity to position the body is presently limited, as we’re initially focused on Tabs use cases.

We invite everyone to participate in our EAP and try out the new macro type. To join us, please fill out this signup form.

9 February 2024

Deprecation Notice Deprecation of inline-marker-ref and inline-original-selection from inline-comments endpoints

The inline-marker-ref and the inline-original-selection response fields from the inline-comments API are being deprecated on February 9th, 2024. Apps should switch to using inlineMarkerRef and inlineOriginalSelection, respectively. On August 9th, 2024, the deprecated fields will be removed. See the documentation for more information.

More details

These fields are located under the properties subheading for relevant API endpoints.

Examples of affected endpoints include:

  • Get inline comments

  • Get inline comment by id

  • Get children inline comments

  • Get inline comments for page

  • Get inline comment for blog post

  • Update inline comment

Announcement Changes to atl.general webitem

As part of the Fixed Page Header feature, we’re making two changes that could affect developers:

  1. The View Page Page header is now fixed at the top of the page to increase accessibility to view page buttons. The header used to scroll away and pop back in if you scrolled up.

  2. Along with the view page header, we’ve also made the atl.general webitem fixed at the top. In the past, the atl.general would only show if the user was at the very top of the page. Now, the atl.general location is fixed and will always be visible above the view page header.

Added New endpoint in Space metadata in Confluence GraphQL APIs

We are adding totalCurrentBlogPosts as a new endpoint to Space metadata in Confluence’s GraphQL APIs.

This returns the total number of blog posts in a space on Confluence.

6 February 2024

Added Get Attachment Comments by Attachment Version in the Confluence Cloud v2 REST APIs

We’ve added the ability to specify an attachment version when requesting attachment comments. To get comments associated with a specific attachment version, use the new version query parameter.

For more information, see Get attachment comments.

5 February 2024

Deprecation Notice Default realm migration downtime will be reduced for Connect apps in August 2024

After observing several successful realm migrations for Connect apps, we have determined that the default downtime window of 24 hours is too long for most apps.

To improve customer experience and better reflect the true downtime needed for most Connect apps to migrate data, we will be reducing the default downtime window to 2 or fewer hours starting early August, 2024 and enabling partners to declare their own downtime.

Understanding that some apps may require more than a few hours to complete data residency migrations, the ability to define a maxMigrationDuration for data residency realm migrations will be made available prior to the implementation of this change. This will enable apps to declare up to 24 hours of downtime, where they have large amounts of data or complex data storage. If you fail to update your downtime window and a migration takes longer than the default, your migration may fail.

We will provide instructions on how to update your app descriptor with a custom downtime window in the coming months in preparation for the change. Keep an eye out here in the change log for more information in late March/early April.

More details

Realm migration allows customers to request app data be moved to the same region as the host product via the Data Residency tab in admin.atlassian.com.

Today, apps built on Connect can support both realm pinning and realm migration to help customers keep their data in a region they trust.

Read more about data residency for Connect apps →

Rate this page: