Details
-
Bug
-
Resolution: Obsolete
-
Medium
-
39
-
Severity 2 - Major
-
16
-
Description
NOTE: This bug report is for Confluence Cloud. Using Confluence Server? See the corresponding bug report.
We're releasing collaborative editing on an opt-in basis for now, so that you can determine if switching it on is the right thing for your instance at this time. This is due to the fact that there'll be no migration path from Confluence Cloud to Server once an administrator has opted-in to use collaborative editing. This is a temporary situation, which will be resolved when we release collaborative editing to Confluence Server in version 6.0.
If you're currently planning a Cloud to Server migration:
Over the coming weeks you may receive in-product notifications asking if you would like to enable collaborative editing. You can click through to read more about the feature, but you shouldn't proceed to opt-in as this means you won't be able to migrate to Confluence Server until we release collaborative editing to Confluence Server in version 6.0.
It's no longer necessary to request a freeze for your Confluence instance to retain the ability to migrate from Confluence Cloud to Server. If your instance is already frozen for this reason, you can reach out to our support team to unfreeze it.
The collaborative editing feature is now compatible with site backup and restore, and no longer prevents migrating from Confluence Cloud to Server.
Attachments
Issue Links
- is related to
-
CONFSERVER-40612 Temporary lack of migration from Confluence Cloud to Server for instances that have opted-in for collaborative editing
- Closed