Confluence 6.13 Release Notes

Highlights

Run Confluence with AdoptOpenJDK 8

Oracle will stop providing public updates for Oracle JDK 8 in January. This means that only Oracle customers with a paid subscription or support contract will be eligible for updates.

In order to provide you with another option, we now support running Confluence 6.13 with AdoptOpenJDK 8. AdoptOpenJDK is free to use, and provides regular maintenance and security updates. Paid support for AdoptOpenJDK is also available from organisations such as IBM.

We’ll continue to support running Confluence with Oracle JDK / JRE 8, and also plan to introduce support for Java 11 in a future release.

Supporting your GDPR efforts

General Data Protection Regulation (GDPR) compliance is front of mind for most organisations right now, and we know many of you are keen to adopt best practices, even if you aren’t subject to the EU regulation.

In this release we’ve added the ability to permanently delete a user account and anonymise much of the personally identifiable information associated with it. There are some limitations, but we think this will be a useful tool for many organisations.

Delete accounts, wherever they’re managed

Deleting a user account is very straight forward. If Confluence can write to the directory they’re stored in, all you need to do is head to User Management, look up the user and click Delete.

If Confluence can’t write to the directory, or if they’re present in several directories, it’s a two-step process. Remove them from all external directories, then head to the new Unsynced from Directory tab in User Management, and delete them from there.

When you delete an account, Confluence will:

remove their account, profile picture (avatar), and personal information
replace their full name and username with an anonymised alias
reindex any content they’ve contributed to or been mentioned on, so their name doesn’t appear in search results.

What happens to people’s content after they’re deleted?

Deleting a user account does not remove any pages, comments, or other Confluence content. We also don’t delete their personal space, as this may contain content owned by your organization.

This means that there will be some additional work to do after their account has been deleted to remove their personal space, and locate any references to the person in free text, or stored by third party apps or Synchrony in the database.

How deleted accounts appear to other people in your site

When an account is deleted, the full name is replaced with an alias like ‘user-12345’ in places including the dashboard, page history, @mentions, and macros. The username is replaced by a user key (a unique string of characters).

The alias stays the same throughout the site. This means that people can see that pages and comments were made by the same person, but not the identity of that person.

Delete vs disable an account

In most cases, when someone leaves your organisation or no longer needs access to Confluence, the existing process to disable a user is adequate. Their name remains attached to their content, and you can easily re-enable their account if they return.

PDF export improvements

If you regularly need to create PDFs of your content, you’ll be pleased to know that we’ve resolved a bunch of PDF export bugs, and made several visual improvements to our PDFs. Some highlights:

Tables better match their Confluence counterparts, no longer filling the whole width, or forcing the columns to be equal width.
Headings have been refreshed, with more consistent sizing.
Ugly ducklings like the recently worked on, status, and tip macros now display more consistently.
Each Confluence page starts on a new PDF page, making your documents easier to read.
Long words and strings now wrap correctly.

We’ve kept the styling of the PDF plain and simple, giving you the perfect blank canvas to add your own style and flair, via the PDF stylesheet.

Moving to the Cloud has never been easier

The Cloud Migration Assistant for Confluence is now bundled with Confluence 6.13. If your team is currently considering a move to Atlassian Cloud, the Migration Assistant will make your day.

Migrate spaces at your own pace

Use the Migration Assistant to analyse the amount of content in your current site, and make plans to move spaces to your new cloud site.

It’s up to you which spaces to migrate, and when. For example you may choose to migrate a few spaces relating to a particular project first, or migrate the spaces belonging to teams in a particular location, to limit disruption to these teams during their working hours.

You’re in control. You choose which spaces to migrate, when to run the plan, and can monitor the migration progress in real time. While one space’s data is being uploaded, the next space’s data is being exported from your database.

Securely transfer your data

We take your security seriously. There’s no need to make changes to your firewall to allow incoming traffic. Just allow outgoing traffic from your Server site to our migrations.atlassian.com service and your new cloud site, and you’ll be off and running.

Good to know

The Migration Assistant only transfers spaces. It doesn’t migrate your users. We recommend populating your new cloud site with users first, so people are seamlessly reunited with their content.

Curious? Head to Cloud Migration for everything you need to decide, plan and migrate your Confluence Server site.

Infrastructure recommendations

Running a large Confluence site and want to make sure your current infrastructure is up to the task?We recently ran a series of performance tests on a typical large-sized Confluence instance. We designed these tests to get useful, data-driven recommendations for your deployment’s application and database nodes. These recommendations can help you plan a suitable environment, or check whether your current instance is adequate for the size of your content and traffic.

Head to Infrastructure recommendations for enterprise-scale Confluence instances to check out our recommendations, including full details of our methodology.