-
Type:
Suggestion
-
Resolution: Unresolved
-
Component/s: Page - Editor - Cloud
-
None
-
2
Display a persistent, non-dismissible banner at the top of the editor area when a diverged unpublished draft is detected. For example:
⚠️ You are editing an unpublished draft. This draft contains changes that differ from the last published version. View differences | Discard draft and start from published
Problem Definition
When a user opens the Confluence editor on a page that has an unpublished collaborative draft (shared draft), the editor silently loads the draft content instead of the published version. There is no visual distinction between "editing the published page" and "editing a diverged draft."
This causes confusion because:
- The user sees content that is different from what they saw on the published (view) page
- They may assume this is a bug or data corruption and open a support case
- The only way to discover the divergence is to manually navigate to the Revert option (⋯ menu → Page history → Revert), which opens a diff comparison — but this is not discoverable
- Users who are unaware of the shared draft mechanism may make edits on top of the stale draft, compounding the divergence
This is especially common in enterprise environments where pages may be edited by multiple users and drafts can linger after a user exits the editor without publishing.
- is related to
-
CONFCLOUD-82339 Page Content Reverts in Edit Mode After Macro Migration
-
- Gathering Impact
-
-
CONFCLOUD-71499 Changes made to a draft with REST API won't take effect on the editor
-
- Short Term Backlog
-
-
CONFCLOUD-75745 Improve move pages error and progress messages
- Gathering Interest
-
CONFCLOUD-77873 Confluence Cloud - Automation - Smart Value | Variables for users
- Gathering Interest
-
CONFCLOUD-84450 While publishing page using API endpoint, the existing draft content must be preserved
- Gathering Interest