Preparing for Confluence 7.10
This documentation is intended for Confluence developers who want to ensure that their existing plugins and apps are compatible with Confluence 7.10.
Watch this page to find out when a new milestone is available and what’s changed. We will publish formal release notes once we release a beta.
Latest milestone
| 8 December 2020 | 7.10.0-rc1 | Download |
Issues with this milestone?
Hit the Feedback button on the Confluence EAP header or raise an issue to tell us about it.
On this page:
Planned changes
In this section we'll provide an overview of the changes we intend to make, so you can start thinking how it might impact your app. We'll indicate when a change has been implemented, and in which milestone.
Seraph upgrade
Status: COMPLETE
In this release we're upgrading atlassian-seraph from 4.0.4 to 4.1.0, which removes the ability to use query parameters to log in. This might affect your development environment and automated tests:
- If you're starting Confluence with AMPS in dev mode (
atlassian.dev.mode=true) this change won't affect you. - If you're relying on the
os_username+os_passwordquery parameter for faster logins, you'll need to add theatlassian.allow.insecure.url.parameter.login=truesystem property. We've used this workaround in several of our builds. - If you're using the stateless test runner, you can add the
use.form.login=truesystem property to your test config, for slower, but safe builds which more closely match how end users use the product.
XStream upgrade
Status: COMPLETE
We're upgrading the version of XStream bundled with Confluence. This is a major upgrade that breaks compatibility with the old format of stored data. To help with this, we are adding a layer of backward compatibility to support existing data in Bandana.
See XStream 1.4 upgrade for full details.
The special milestone is no longer available as this change is now available in 7.10.0-m43.
OAuth 2.0 authentication
Status: DELAYED
We're adding the ability to configure OAuth 2.0 authentication. Within Confluence this will mostly be used for mail server authentication (such as a POP3 incoming mail server), but will also be available to apps.
We're still working on the mail server configuration screens in Confluence, that will allow you to select OAuth 2.0 as the authentication method, so we've rolled back the OAuth 2.0 changes for now.
Update : The mail server configuration part of this work has been put on hold indefinitely. Confluence 7.17 will include the ability to configure Confluence as an OAuth 2.0 client and provider, allowing it to exchange data with external applications in both directions.
Create and reply by email
Status: DELAYED
We've been improving the Create by email and Reply by email plugins. These plugins have always been disabled by default, and were quite difficult to use because there was no UI for configuring the feature.
We're making some improvements to the way the feature works, and adding a new admin screen which administrators can use to enable the features.
Update : This work has been put on hold indefinitely.
Jira Service Desk is now Jira Service Management
Status: COMPLETE
As you may already be aware, from version 4.14 Jira Service Desk becomes Jira Service Management. In this release we've updated the places in Confluence that refer to Service Desk to now refer to Service Management. This is just a visual change, and has no impact on compatibility.
Removal of editor-v3
Status: ADVANCE NOTICE
When we upgraded our editor to TinyMCE v4 way back in Confluence 6.14, we introduced an unsupported dark feature that could be used to revert to the v3 editor (frontend.editor.v4 / frontend.editor.v4.disable). We plan to remove this dark feature flag in a future Confluence release, as they are no longer tested or reliable.
Once that happens, the editor-v3 WRM context will no longer be loaded. Any resources used only in this context can be removed completely. The editor and editor-v4 contexts are unchanged, and with this change, resources in editor-v4 can be safely moved to editor.
Implemented changes
In this section we'll provide details of changes we have implemented, organised by the milestone they are first available in. This will help you decide which milestone to use when testing.
Release Candidate - 8 December 2020
No significant changes in this release candidate.
Did you know you can easily look up common plugin module versions used in Server and Data Center products? Head to https://bitbucket.org/atlassian/platform-module-usage
Beta 1 - 30 November 2020
In this beta:
- Seraph upgrade. See above for more details.
EAP 2 – 23 November 2020
Milestone 7.10.0-m43
In this milestone:
- XStream upgrade. See XStream 1.4 upgrade for details.
- Upgraded Spring from 5.1.14 to 5.1.18.
EAP 1 – 16 November 2020
Milestone 7.10.0-m32
In this milestone:
- Jira Service Desk is now Jira Service Management in the Confluence UI.
Looking for updated documentation? Check out the Confluence EAP space for the latest docs.
Did you know we’ve got a new developer community? Head to community.developer.atlassian.com/ to check it out! We’ll be posting in the announcements category if when new EAP releases are available.