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.
Forge apps can now access the Get User Email and Get User Email Bulk APIs on Jira and Confluence when declaring the read:email-address:jira or read:email-address:confluence scopes.
Access to the Get User Email and Get User Email Bulk APIs is only supported when making asApp() requests. Requests made asUser() are not compatible with these APIs.
Learn more about profile visibility on Forge apps here.
Rollout: Folders are currently in beta as of September 18 and will gradually go live for all customers in the coming weeks! In Progress
Endpoints and scopes have been added for Confluence Folders. For further information about these updates, reference the Atlassian Developer Documentation for OAuth and Forge scopes as well as Confluence Cloud REST API v2.
Three new scopes have been added for Folders: read, write, and delete. These additions will support the implementation of Folders in Forge applications.
Read | Write | Delete |
|---|---|---|
|
|
|
Creation, retrieval, and deletion of Folders have been added for v2 REST APIs. Creation, retrieval, modification, and deletion of properties as well as retrieval of operations and ancestors is supported via these added APIs.
This capability allows a Connect app supporting data residency to remain in the same region which the app was originally installed for up to 30 days after uninstall. This allows customers to reinstall an app without suffering data loss by being pinned to a different region
We are simplifying the left nav experience for Confluence users, including cleaning up unused features in spaces.
We will turning off blogs in existing Confluence spaces that have not published a blog. While blogs can still be created after this change, users won’t be able to see blogposts in the side navigation until they turn the feature back on in the Edit Features page (Space Settings > Features).
We will be automatically turning off blogs for any newly created space to simplify the left nav experience.
While blogs can still be created after this change, users won’t be able to see blogposts in the side navigation until they turn the feature back on in the Edit Features page (Space Settings > Features).
This change will take place on all forms of space creation whether the request is coming from the UI, GraphQL, or REST API.
In our v2 Smart Link APIs, we provide HTTP methods for creating and getting Smart Links in the content tree. Previously, the URL embedded as the Smart Link in the content tree was inaccessible from these APIs (as reported here); now, they are provided in the response payload under the “embedUrl" property key (if present).
We are removing atl.list-templates and atl.list-templates.after from Confluence Connect web panels. These extension points will no longer be available to apps that modify admin settings.
Following its preview release back in February, Adopting Forge from Connect is now generally available.
The majority of apps can now incrementally adopt Forge with their existing Connect apps. The remaining apps will be able to do so when Data Residency support is available for Forge Remotes.
Learn more in our blog post - Connect apps will gain new extensibility features through Forge
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.
You can now migrate existing Connect macros to the native Forge macro module.
This change allows your app to render existing Connect macros in Confluence pages as Forge macros, when you adopt a Forge macro with a key matching the Connect macro.
See Migrate a macro module from Connect to Forge to get started.
A new RFC is ready for review at https://community.developer.atlassian.com/t/rfc-63-page-extension-in-editor-design-changes-and-more/83196/1 .
We've updated the docs for /wiki/rest/api/user/bulk to reflect the accountId limit of 100. It previously inaccurately stated 200, which wasn't the case, due to request header size limits https://developer.atlassian.com/cloud/confluence/rest/v1/api-group-users/#api-wiki-rest-api-user-bulk-get .
The ‘limit’ parameter was removed, as the endpoint already returns the number of results corresponding to the number of accountIds in the payload, up until the hard limit of 100.
More details can be found here.
We're announcing new IP ranges that will soon be available for requests from external clients, such as browsers and API integrations:
13.35.248.0/24
13.227.180.0/24
13.227.213.0/24
These ranges won't be used to make outgoing connections from Atlassian Cloud to remote systems, for example, webhooks.
To prepare for this change, update your firewalls and other security measures to allow connections to the new IP ranges.
For more information, see IP addresses and domains for Atlassian Cloud products, which includes instructions on how to receive notifications of changes, as well as links to machine-readable lists of our IP ranges.
We've released a substantial enhancement to the Connect Data Residency migration experience.
The Downtime Estimation feature is now in preview.
Marketplace Partners can now report the estimated migration downtime, ranging from 0.5 hours to 24 hours. This helps admins approximate the time to completion and coordinate operations while minimizing disruptions.
Connect modules in Connect apps adopting Forge can now support internationalisation. The latest version of the connect-to-forge package will copy over the translations field in a Connect descriptor to a Forge manifest as connectModules.jira:translations or connectModules.confluence:translations based upon the product.
For more information, refer to Incrementally adopting Forge from Connect.
Connect modules in Connect apps adopting Forge can now support statically declared Cloud App Migration webhooks. The latest version of the connect-to-forge package will copy over the cloudAppMigration field in a Connect descriptor to a Forge manifest as connectModules.jira::cloudAppMigration or connectModules.confluence::cloudAppMigration based upon the product.
For more information, refer to Incrementally adopting Forge from Connect.
The Cloud App Migration support in apps adopting Forge from Connect will continue to only support the migration of Connect modules. For more details, please refer to Limitations and Differences.
Rate this page: