• 2
    • 1
    • We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.

      When editing a page, it would be beneficial to be able to consciously discard the draft. Often the user realizes that the changes were absolutely not needed, but has to go through a further three-step process (either re-editing, clicking Discard then clicking Save or going to the profile drop-down menu, selecting Drafts, then clicking Discard by the page).

      Even if there is a Discard Verification dialog box to click through, it would be a much better solution.

            [CONFSERVER-38764] Add Discard option to Save and Close in edit mode

            Nas Banov added a comment -

            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!

             

            Nas Banov added a comment - 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!  

            Amber W added a comment -

            I am with @Nico Kadel-Garcia!

             
             
            nkadel1035724755 added a comment - 27/Jun/2017 10:31 AM
            It would be far safer to have "Publish", "Save", and "Discard" rather than the curent "Publish" and "Close".

            The word "Close" is unclear and inconsistent with many, many other applications for which "Close" discards unsaved content.

            Amber W added a comment - I am with @Nico Kadel-Garcia!     nkadel1035724755  added a comment - 27/Jun/2017 10:31 AM It would be far safer to have "Publish", "Save", and "Discard" rather than the curent "Publish" and "Close". The word "Close" is unclear and inconsistent with many, many other applications for which "Close" discards unsaved content.

            I thought this was a bug and came across this to find that it's how it was built???? I don't understand not having a discard or even cancel feature which does not save this version. A little frustrating as anytime I choose to edit this page, the previous edit shows us which I don't want to use to edit the new version.

             

             

            Antonio Smith added a comment - I thought this was a bug and came across this to find that it's how it was built???? I don't understand not having a discard or even cancel feature which does not save this version. A little frustrating as anytime I choose to edit this page, the previous edit shows us which I don't want to use to edit the new version.    

            How will this interact with collaborative editing? Can collaborative editing be turned off? In my opinion, it's more trouble than it's worth.

            Aaron Miller added a comment - How will this interact with collaborative editing? Can collaborative editing be turned off? In my opinion, it's more trouble than it's worth.

            is there any workaround please?

            Peter Hozák added a comment - is there any workaround please?

            It would be far safer to have "Publish", "Save", and "Discard" rather than the curent "Publish" and "Close".

            The word "Close" is unclear and inconsistent with many, many other applications for which "Close" discards unsaved content.

            Nico Kadel-Garcia added a comment - It would be far safer to have "Publish", "Save", and "Discard" rather than the curent "Publish" and "Close". The word "Close" is unclear and inconsistent with many, many other applications for which "Close" discards unsaved content.

            I just removed all my drafts but the page still has "Unpublished changes" that I can't get rid of! Did the person designed this "feature" have ever attempted to use Confluence?

            Dmitry Belyaev added a comment - I just removed all my drafts but the page still has "Unpublished changes" that I can't get rid of! Did the person designed this "feature" have ever attempted to use Confluence?

            Agree with the comments above.  It's as if Atlassian don't use Confluence themselves so don't get why this is needed.  This just quickly creates a junkyard of drafts that will never be cleaned up by the average user.

            Rob Overell added a comment - Agree with the comments above.  It's as if Atlassian don't use Confluence themselves so don't get why this is needed.  This just quickly creates a junkyard of drafts that will never be cleaned up by the average user.

            Please reinstate the option to Cancel and edit or Discard changes.

            I want this almost daily and totally fail to understand how Atlassian thought removing this was a good idea.

            Dave Noonan added a comment - Please reinstate the option to Cancel and edit or Discard changes. I want this almost daily and totally fail to understand how Atlassian thought removing this was a good idea.

            I agree with Matt.  This was a poor decision by Atlassian to rollout.  Again, it comes down to providing details to admins so they can communicate the changes as well as feedback from the community.  

            blaine stussy added a comment - I agree with Matt.  This was a poor decision by Atlassian to rollout.  Again, it comes down to providing details to admins so they can communicate the changes as well as feedback from the community.  

              Unassigned Unassigned
              bd662fecf73e Milo Test
              Votes:
              88 Vote for this issue
              Watchers:
              50 Start watching this issue

                Created:
                Updated: