Confluence 7.10 beta release notes
Development releases are not production ready. Development releases are snapshots of the ongoing Confluence development process. While we try to keep these releases stable, they have not undergone the same degree of testing as a full release, and could contain features that are incomplete or may change or be removed before the next full release.
No upgrade path. Because development releases represent work in progress, we cannot provide a supported upgrade path between development releases, or from any development release to a final release. You may not be able to migrate any data you store in a Confluence development release to a future Confluence release.
Atlassian does not provide support for development releases.
Issues with this beta?
Please raise an issue to tell us about it.
Highlights of 7.10.0-rc1
Released 7 December 2020
No significant changes in this release candidate.
Highlights of 7.10.0-beta1
Released 1 December 2020
Jira Service Desk is now Jira Service Management
Jira Service Management is an IT service management (ITSM) solution built on Jira to help IT operations and development teams collaborate at high velocity. It empowers teams to respond rapidly and provide great customer service.
All references to Jira Service Desk in Confluence have been changed to Jira Service Management. There's been no changes to any of the great features, including knowledge base integration.
Learn more about Jira Service Management
Clean up your Confluence site
A side effect of a big, busy Confluence site is the huge amount of content created. Over time, this can really build up, and clean up becomes essential.
Our new guide gives you plenty of hints and tips for improving findability and reducing the size of Confluence's footprint. From archiving spaces, to identifying large attachments, there's a range of strategies to help you keep Confluence lean and clutter free.
Learn how you can clean up your Confluence instance
We're planning some more improvements in this area, and can't wait to share them with you in a future release.
Upgrade make take longer than usual
The XStream upgrade mention below requires an upgrade task to update data in the bandana table (often used by app to store data). Depending on the size of these tables, the upgrade task may take some time. In our test site (classified as large, with a lot of apps) it took approximately 2 hours to complete.
In this release we upgraded the version of Xstream bundled with Confluence. This is a major upgrade that may have an impact on custom apps you may have developed.
See XStream 1.4 upgrade for full details.
You may find that some Marketplace apps are not compatible with Confluence 7.10 on release day. We recommend upgrading Confluence in a test environment, and checking that all your apps start up and work as expected, so you don't get any surprises when you upgrade. If you do find an app doesn't start up, contact the app vendor for assistance.
PostgreSQL driver upgrade
We've upgraded the PostgreSQL driver bundled with Confluence from 42.2.6 to 42.2.16. We don't expect there to be any impact. See the PostgreSQL JDBC driver changelog if you want more details.
Login with query parameter no longer supported
From Confluence 7.10 we will prevent you from using the
os_username+os_password query parameter to log in.
If you have any custom integrations that use this method, you should switch to basic authentication, or consider a more secure option, such as personal access tokens.
If you need more time to update your integrations, you can set the
atlassian.allow.insecure.url.parameter.login system property to
true as a workaround.
Supported platforms changes
No platform changes planned for this release.
Confluence 7.10 contains changes that may affect apps. Head to Preparing for Confluence 7.10 to find out how these changes will impact app developers.
Was this helpful?Yes Provide feedback about this article