Confluence 7.6 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.6.0-rc1
Released 22 June 2020
We discovered an issue with our latest changes to the audit log, so have rolled back a few of these changes. We expect category filter, and new log file retention settings to be available in Confluence 7.7, which will be here before you know it.
Highlights of 7.6.0-beta3
Released 18 June 2020
This beta fixes an issue that was causing upgrades in AWS to fail.
Highlights of 7.6.0-beta1
Released 15 June 2020
More control of your audit log
For DATA CENTER
Filter by category DELAYED
Audit log events are organised into categories. You can now filter the log by one or more categories. This is particularly useful if you want to see just security and authentication events, for example.
More events to capture end-user activity
Keep a closer eye on what users are doing in your site with new events that cover when someone:
- moves a page or blog post
- shares a page or blog post
- requests access to a page or blog post
- grants access to a page (from an access request)
These events are in the Advanced coverage level, which is available with a Data Center license.
Change log file retention settings DELAYED
In Confluence Data Center, we write events to an audit log file in your local home directory. This file can be used as an additional record, and when integrating with third-party logging aggregation tools.
Previously the number of log files stored were limited to 100. This is now configurable, so you can store more, or less as you need. The maximum size of these files is 100 MB, so make sure you've provisioned enough disk space on each node.
Trusted domains for Companion app
For SERVER DATA CENTER
System administrators can now set trusted domains/sites before rolling out the Companion app to all users. Setting your Confluence URL as a trusted domain means users don’t have to select 'Trust this domain' when they edit a file for the first time. Easily set trusted domains with an environment variable or during MSI install.
Requires Companion 1.2.0. You don't need to upgrade Confluence for this improvement.
Unlocking Data Center potential
In this release we've made some changes to our caching architecture which will improve cluster resilience, and unlock greater scale opportunities in future releases.
Changes to mobile login
The Confluence Server mobile app needs to check that you're running a compatible version of Confluence before it can log you in. If you've configured a custom filter in your VPN or firewall to prevent unauthenticated requests to your server, Confluence can't perform this check. Previously the solution was to allow
<confluence-base-url>/server-info.action and several headers and cookies.
From Confluence 7.6, you will only need to allow
Supported platforms changes
No platform changes planned for this release.
Confluence 7.6 contains changes that may affect apps. Head to Preparing for Confluence 7.6 to find out how these changes will impact app developers.