Confluence 7.2 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.2.0-rc2
Released 6 December 2019
This release candidate contains fixes for a few issues we found in RC1.
Highlights of 7.2.0-rc1
Released 4 December 2019
No significant changes in this release candidate.
Highlights of 7.2.0-beta1
Released 27 November 2019
Access Data Center features on your current infrastructure
Data Center was originally designed as a clustered deployment option to help enterprises increase application uptime, and maintain performance at scale.
Now, you can access all of these features on your current Server infrastructure simply by applying a Data Center license. Clustering is still available and ready to enable when you want to scale, but it’s no longer required as part of the license upgrade.
Learn more about the full set of features available with a Data Center license.
Using Companion app in single sign-on environments
If you've configured single sign-on (SSO) in such a way that your reverse proxy redirects the requests to your SSO gateway, and only successfully authenticated requests ever reach Confluence, your users won't have been able to use Atlassian Companion app. This is because the Atlassian Companion app uses JWT tokens to authenticate requests, and only Confluence can authenticate these requests, not your SSO authenticator.
To make sure requests from the Atlassian Companion app can be authenticated, you can now configure your reverse proxy to always allow requests from the following URLs:
<base-url>/rest/analytics/1.0/publish/bulk(only necessary if you have opted in to data collection)
If an unauthenticated user tries to access these URLs directly, they would be redirected to the Confluence login screen. They wouldn't be able to access any content or download files while unauthenticated.
Chart macro maximum size
We now limit the maximum height and width of the Chart macro. This will help avoid performance problems if a user accidentally enters a very large value, as we'll automatically resize the chart to 3000px by 3000px. You can modify the default maximum using the following system properties:
Minor change to Lucene implementation
We've made a change to the implementation of the term filter. A bitset is now only created when the number of matches is large enough to benefit from it. This helps reducing unnecessary CPU and memory usage and avoid bottlenecks. The threshold can be changed via the
confluence.search.lucene.termFilterBitSetThreshold system property, but we don't expect you should need to do this.
Supported platforms changes
- Added support for MySQL 8.
- Advance notice: Confluence 7.3.x will be the last release to support PostgreSQL 9.4, MySQL 5.6 and Oracle 12c R1. See End of Support Announcements for Confluence for more information.
Confluence 7.2 contains changes that may affect apps. Head to Preparing for Confluence 7.2 to find out how these changes will impact app developers.