Hello

Still waiting for a fix. It is just amazing that this small feature was not part of the initial feature.
UX = User eXperience ... and here it is very bad.
When will it be available ?

To me it seems absolutely ridiculous that I can't easily discard my own changes. If I edit a page, make a couple changes, then change my mind and hit Close - if anyone else is editing the document then the default option is to discard their changes too?? How does that make any sense whatsoever?

We recently migrated to Confluence cloud and while the collaborative editing is great in general,  the inability to discard edits as could be done in the old version is terrible. I can't believe this ridiculous usability issue and terrible workaround has existed over a year–this is not what I expect from Atlassian!

The workaround is embarrassing – I spent far longer trying to discover what I thought I must be missing, ultimately to end up digging in here to find nearly 50 folks have voted on this ticket to resolve it (so likely 1000s have encountered it and been likewise frustrated). Given it's been over a year and fix is not scheduled, please throw your users a bone, such as with  icon next to 'Close' that explains workaround if you want to discard changed in the interim. 

Way to go, "collaborative editing mode"! Even on pages that nobody else is editing, even to page that i "own", there is no way to revert to published content and lose auto-saved defective version. 

i am currently in ridiculous state with a page in my personal space - it had recorded that i have some unpublished change, yet that does not show under Drafts. And that unpublished change is some older or out-of-sync version, since i have made new edits to the page - so i really want to lose that auto-saved version but there is no way to do that!

So, how long is this going to have to stay in Gathering Interest status? This is a dangerous "feature" and there is more than one ticket open asking for a new solution to be developed (i.e. allow discarding of personal changes, locking discard altogether, etc.)?

One alternative solution would be to allow users to lock pages for a time so that only they can edit it.

This would avoid the risk of users accidentally and unintentionally engaging in collaborative editing, which is the typical reason one would need to rollback one's own changes without affecting others'.

I would also like this feature to be improved. Whilst Collaborative Editing has many useful features, we've switched it off purely because of the lack of ability allowing users to remove or publish their own drafts.