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.
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.
The createFrame helper function simplifies the communication between the UI Kit and Frame components. It enables the creation of custom Frame components with support for passing custom properties from UI Kit to Frame component resources as simple React component properties.
For more information about how to use the createFrame helper function, see here.
Confluence admins will be getting the ability to rename space keys. This EAP is to allow for early access and testing of 3rd party apps as well as any other interested parties.
The ability to change a Space key has garnered significant interest from numerous customers. Customers frequently request the capability to rename space keys due to organizational changes such as modifications in team or project names, acquisitions by other companies, organizational restructuring, or alterations in user names. Furthermore, unchangeable space keys creates obstacles when attempting to migrate spaces between Confluence instances with identical space keys.
This functionality addresses one of the most requested features in Confluence: allowing users to rename space keys.
To address this, we created the concept of Space Aliases. When you go to Space Settings, Space details, and Edit Space Details, you will see the “Space key:” field is editable. Note that, like the original space keys, these space aliases need to be unique across all spaces.
In places where you see space keys, you will see the new alias, and the alias can be used anyplace a space key currently can be used.
For developers, we kindly request that you refrain from scanning URLs to parse space keys. If this is currently being done, we strongly recommend transitioning to AP.context.getContext() or utilizing our V2 Space API to obtain the correct space key from its response.
Since the alias field is subject to change, it is recommended to avoid using aliases to store your application data. Instead, opt for using the Space ID whenever feasible. We want to ensure app developers have access to this change early so they can identify any issues this causes to their apps. For additional context about this EAP, please refer to our RFC-54 Introducing Space Alias in the Confluence URL.
By signing up for this Early Access Program (“EAP”), you acknowledge the Atlassian Privacy Policy and that:
Early access to Space Aliases is governed by the Atlassian Customer Agreement (“ACA”). This feature is considered a “Free or Beta Product”, as set forth in Section 17 of the ACA and is subject to applicable terms, conditions, and disclaimers.
Early access to updated Space APIs is governed by the Atlassian Developer Terms. These APIs are considered “Early Access Materials”, as set forth in Section 10 of the Atlassian Developer Terms and are subject to applicable terms, conditions, and disclaimers.
The documentation for this EAP is available at https://forms.gle/G6yZxWARL366oQna8.
On August 22, 2024, the functionality of /wiki/rest/api/user/bulk will change. The 'limit' parameter will no longer be functional for GET /wiki/rest/api/user/bulk operation; rather, the number of accountIds passed in will reflect the dictate the number of results returned. If your code sends the limit parameter, the API will ignore it.
Also, due to request header size limits, a maximum of 100 accountIds may be specified in a request. If you specify more than 100, only the first 100 will be returned. The documentation has been updated to reflect the limit of 100. It had previously stated 200, which was incorrect.
More details can be found here.
The upper limit of for Data security policy events has been increased to 200,000 objects, from the previous limit of 50,000 objects.
How does the upper limit work
This means that if a customer activates or updates a data security policy that affects more than 200,000 objects, you will receive the first 200k objects in the events and the rest would be omitted.
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.
Data security policy events are generated when installed apps' access to certain data within Confluence, Jira, Jira Service Management, or Jira Software has been blocked by an administrative policy with an App access rule. App developers can subscribe to these events, we encourage you to read the Developer guide.
The Developer Assistant App, which manages the Developer Canary program, will require additional permissions to function, and therefore all users must approve an update manually.
Atlassian is changing the tools and processes we use internally to manage and roll out changes. We have released a new version of the Developer Assistant App to adapt to this. The old version of the app will stop working after Dec 1, 2024 . All instances currently enrolled in the Developer Canary program will stay enrolled, however you will need to install the new version of the Developer Assistant app to change your enrollment status.
This follows an RFC detailed in this Developer Community thread.
For more information about the Developer Canary program, or installing the Developer Assistant App, please see this page.
We have removed existing duplicate content properties and existing duplicate space properties from the response of our Confluence V2 REST APIs.
Duplicate content properties refer to content properties with different ids that have the same content property key and that are associated with the same piece of content.
Duplicate space properties refer to space properties with different ids that have the same space property key and that are associated with the same space.
From a set of duplicates, only the most recently created – or the one with the larger property id – is kept.
Endpoints affected include:
On Jul 30, 2024, we will begin rolling out a fix for Forge apps which declare the Connect lifecycle module to use a distinct shared secret that changes on major versions instead of a single shared secret like it is currently.
The history of why we are making this change and why we want to move to this secret model is outlined here. If you’ve followed the previous post, we expect no functional changes for app developers. Please ensure your apps are storing and maintaining secrets on a per-installation basis.
On Jul 30, 2024, new Connect on Forge app installations, major version upgrades, and Connect to Forge migrations will start receiving distinct shared secrets.
After Aug 7, 2024, we will be rotating the secrets of existing Connect on Forge app installations to move them to distinct shared secrets. A new installation payload containing this secret will be shared.
These changes will be rolled out on a per-tenant basis.
We are pleased to share that the customer experience for Connect data residency is now generally available. This is inclusive of the data residency UI in the admin hub, which offers admins a clear and easy way for admins to manage their data.
Learn more about data residency for Connect Apps.
As we share this announcement with customers, Atlassian has encouraged customers to explore data residency options for their apps. Please be aware that this may result in a slight uptick in customer support inquiries concerning data residency.
Data residency for Connect apps is just one more way to make meeting a key customer trust requirement easier than ever. It enables Atlassian organization administrators to specify where subsets of their product data at rest are hosted.
To take advantage of data residency for your Connect-hosted app, you’ll need to store any in-scope data (data that’s in-scope for data residency) in Connect. Then, update:
Your manifest so Atlassian is aware of your data residency offering
Your Privacy & Security tab so that customers know about your app’s support for data residency
Connect apps adopting Forge can now register, retrieve and delete new and existing dynamic modules.
For more information, refer to Incrementally adopting Forge from Connect.
Today, we are starting the gradual roll out of a new selection / configuration control for macros in the Editor that will make it easier to configure macros while editing in Confluence, starting with sites in the Developer Canary Program and a portion of users. No updates or work will be required by app makers.
To see this in action, check out More details below.
Thanks to all who left feedback in the RFC!
Connect apps registered on Forge are no longer able to set `app.connect.authentication: oauth2` in their manifest. This caused client credentials to be sent in the installation hook that could be exchanged for an api.atlassian.com access token. Developers wishing to make requests to api.atlassian.com from their app server should use Forge Remote instead. If you were relying on this feature, we’re happy to answer questions you may have about migrating on the Developer Community forums.
The ability to specify the url of the smartlink object you are creating has been added! The documentation for this endpoint, and the arguments for it can be found here: https://developer.atlassian.com/cloud/confluence/rest/v2/api-group-smart-link/#api-embeds-post.
Forge functions can now interact with remote backends utilising Forge Remote. This capability makes it simpler and more secure to integrate remote backends with your Forge app.
See Forge Remote - Calling a remote backend from a Forge function for more information.
Data classification is now available for Whiteboards and Databases. We have rolled out a set of Confluence Cloud REST API v2 to classify whiteboards and databases.
Whiteboard Classification Level
Database Classification Level
UI Kit data visualizations components are in Early Access Program (EAP).
We now have the following data visualization components to organize and present data:
Bar chart
Stack bar chart
Horizontal bar chart
Horizontal stack bar chart
Line chart
Pie chart
Single value
To start using this EAP, sign up using the Forge EAP form.
For more information about how to use the components, see here.
Rate this page: