-
Type:
Bug
-
Resolution: Not a bug
-
Priority:
High
-
Component/s: Migrations - Site - Cloud to Cloud Migration
-
None
-
2
-
Minor
-
1
-
Warranty
Issue Summary
Content status settings isn't restored on the destination Confluence site.
This happens on both BRIE and C2C migration approach.
Steps to Reproduce
- On Confluence A, enable Content status settings
- Under "Suggest statuses", delete the statuses and add some custom statuses.
- Data migration:
- BRIE: Backup Confluence and restore it to a new Confluence site
- C2C tool: Perform a migration from Confluence A to Confluence B
- Review the list of "Suggest statuses" on destination Confluence
Expected Results
As per suggested on the following documents, Content status settings will be restored.
Actual Results
- contentstates data was not exported
- "Content status" data isn't restored
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available.
- is duplicated by
-
CLOUD-12785 Confluence Cloud Migration - "Suggest statuses" and custom statuses data aren't migrated
- Gathering Interest
- mentioned in
-
Page Loading...