• 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.

          Form Name

            [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.

             

             

            Deleted Account (Inactive) 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.  

            Matt Styka added a comment -

            This change just got rolled out and it's seriously affecting page editing on a few fronts:

            • It requires multiple clicks now to back out of edit mode. Before you could just click "Close" and none of your changes would be saved (One action). Now I have to do the following: Click Back, read the modal (which isn't the simplest to understand since you're "Continuing" to actually "Cancel"), Click that button, then you're taken back. Too many steps for a process that wasn't broken.
            • I have multiple people going in and editing pages at once. If they don't make any changes and click "Save and close", it essentially puts it into a draft mode. Then if I go back in to make my own edits, I get a modal asking me to confirm the changes from the previous user. The problem is, they didn't make any, so it just shows my own. Again, added confusion ...
            • This automatic saving is also causing problems when connectivity isn't perfect. Normally you click edit and all of your content opens immediately. Now because this Auto save was put in, the page sometimes takes a minute to load if not longer. Why is it "Connecting" when you are just going to edit mode?

            Matt Styka added a comment - This change just got rolled out and it's seriously affecting page editing on a few fronts: It requires multiple clicks now to back out of edit mode. Before you could just click "Close" and none of your changes would be saved (One action). Now I have to do the following: Click Back, read the modal (which isn't the simplest to understand since you're "Continuing" to actually "Cancel"), Click that button, then you're taken back. Too many steps for a process that wasn't broken. I have multiple people going in and editing pages at once. If they don't make any changes and click "Save and close", it essentially puts it into a draft mode. Then if I go back in to make my own edits, I get a modal asking me to confirm the changes from the previous user. The problem is, they didn't make any, so it just shows my own. Again, added confusion ... This automatic saving is also causing problems when connectivity isn't perfect. Normally you click edit and all of your content opens immediately. Now because this Auto save was put in, the page sometimes takes a minute to load if not longer. Why is it "Connecting" when you are just going to edit mode?

            In the current cloud version, there isn't even a warning that I am editing a draft. So if I edit a page, regrets it, and later return I am immediately editing the draft. This could have serious consequences, especially on large pages where draft-changes are easily overlooked. 

            Tom Birch Hansen added a comment - In the current cloud version, there isn't even a warning that I am editing a draft. So if I edit a page, regrets it, and later return I am immediately editing the draft. This could have serious consequences, especially on large pages where draft-changes are easily overlooked. 

            It is very frustrating that there is no cancel button.

            Tom Birch Hansen added a comment - It is very frustrating that there is no cancel button.

            When in edit mode, (in my opinion) there needs to be a "Discard" option.

            This is what the options are today (in Cloud):

            Jonathan Hult added a comment - When in edit mode, (in my opinion) there needs to be a "Discard" option. This is what the options are today (in Cloud):

            I agree, this is a missed feature.

            Tom Birch Hansen added a comment - I agree, this is a missed feature.

            Chris Kite added a comment - - edited

            Not having this is extremely frustrating. I often times will open up an existing document to test some edits (maybe a new plugin or test formatting on the existing content or a user is having issues editing). I then just want to cancel all changes and close the editor. Keeping the changes when I choose "Close" is not ideal. I do not want to have to remember to discard the draft and I do not want the next user who edits it to have to worry about the dialog showing an existing draft.

            Chris Kite added a comment - - edited Not having this is extremely frustrating. I often times will open up an existing document to test some edits (maybe a new plugin or test formatting on the existing content or a user is having issues editing). I then just want to cancel all changes and close the editor. Keeping the changes when I choose "Close" is not ideal. I do not want to have to remember to discard the draft and I do not want the next user who edits it to have to worry about the dialog showing an existing draft.

            prior to 5.7.x, there use to be a 'Cancel' button....which was nice.

            Aaron Harshbarger added a comment - prior to 5.7.x, there use to be a 'Cancel' button....which was nice.

            Reto Weiss added a comment -

            The big advantage of such an option would be that the decision (whether to keep or discard the changes) could be taken immediately.

            Reto Weiss added a comment - The big advantage of such an option would be that the decision (whether to keep or discard the changes) could be taken immediately .

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

                Created:
                Updated: