Uploaded image for project: 'Confluence Cloud'
  1. Confluence Cloud
  2. CONFCLOUD-52330

Confluence Creation/Editing Missing the Option to Discard Changes

    • 3
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Atlassian Status as of 30 June, 2017

      The ability to "delete the unpublished draft" / "revert to last published version" from within the editor has been released to all customers. Please view the documentation for further details.

      Of note, this change does not provide the ability to discard just your changes when collaborating with others. This feature request is being tracked separately on CONFCLOUD-45721.

      Phil Oye, senior product manager

      Confluence used to have an option to discard changes, or cancel the page save. This was used in the case of too many unwanted changes to be reverted. Screenshot below is showing Close as that option.

      However, current Cloud releases is missing this option

      Steps to Replicate

      1. On Confluence, click on create page
      2. Notice that there is no option to cancel

      Expected Result

      Ability to cancel the page creation

      Actual Result

      No cancel option nor discard option.

      Workaround

      Save it as draft and discard the draft.
      To access draft,

      Click on user profile and select draft, or use the following link replacing your instance url.
      <instanceurl.atlassian.net>/wiki/users/viewmydrafts.action

      Note
      This is discovered on version 1000.1147.0 and 1000.1161.0

        1. image-2017-05-15-16-21-41-154.png
          23 kB
          Troy Meredith
        2. image-2017-06-26-22-12-14-943.png
          26 kB
          Reha Kocatas
        3. image-2017-06-27-11-44-43-344.png
          26 kB
          philoye
        4. image-2017-06-27-11-45-01-888.png
          53 kB
          philoye
        5. image-2017-06-27-11-45-11-111.png
          161 kB
          philoye
        6. Screen Shot 2017-03-31 at 5.09.00 PM.png
          7 kB
          Richie Gee
        7. Screen Shot 2017-03-31 at 5.10.47 PM.png
          11 kB
          Richie Gee
        8. Screen Shot 2017-05-26 at 11.43.08 am.png
          36 kB
          Desiree Conceicao
        9. Screen Shot 2017-05-26 at 11.46.25 am.png
          86 kB
          Desiree Conceicao

            [CONFCLOUD-52330] Confluence Creation/Editing Missing the Option to Discard Changes

            philoye added a comment -

            philoye added a comment - Good pickup awei , updated link is here:  https://confluence.atlassian.com/confcloud/create-edit-and-publish-724764831.html

            Would you please update the documentation link? It's now "Page Not Found"...

            Alex Wei (DE) added a comment - Would you please update the documentation link? It's now "Page Not Found"...

            I still want the preview button restored . Why are you hiding it?

            Bob Swift {Appfire} added a comment - I still want the preview button restored . Why are you hiding it?

            philoye added a comment -

            Hi bob1734599024, Sorry for the extra click, but the keyboard shortcut Shift+Command+E (Mac) or Shift+Control+E (Windows) will bring up preview.

            philoye added a comment - Hi bob1734599024 , Sorry for the extra click, but the keyboard shortcut Shift+Command+E (Mac) or Shift+Control+E (Windows) will bring up preview.

            Thanks for providing this fix .

            Why do I now need an extra click and position to do a simple preview? . This is a very common thing to do. 

            Bob Swift {Appfire} added a comment - Thanks for providing this fix . Why do I now need an extra click and position to do a simple preview? . This is a very common thing to do. 

            philoye added a comment -

            From the outside, I realise this seems really simple, and you might assume that we're just not listening to you, so let me provide you with a little more background and details.

            Firstly, this was not at all a closed door decision. We do ample user testing, have multiple avenues of collecting feedback, and in order to create this experience, first tested a number of different designs to see which one customers

            • Liked the most
            • Found easiest to use
            • Resulted in the least accidental damage (such as from accidentally deleting someone else's work).

            Secondly, while the ability to cancel your changes has existed for a very long time in various text editors, these are in an environment where concurrent editing is not possible. If a number of people are editing something simultaneously, as with Google Docs, you have a revision history, but you can't remove just your edits. This is because of the nature of collaborative editing - if two people are writing something together, and each makes changes to what the other has written, should 'remove all my changes' remove what the other person has also done? Will it bring back what was changed? Will it delete the other person's work, if they wrote over yours? It's not a simple matter.

            Lastly, while it seems like we might be ignoring you, I assure you that our team reads every piece of feedback we receive and we thank you for taking the time to provide it.

            Thanks,
            Phil

            philoye added a comment - From the outside, I realise this seems really simple, and you might assume that we're just not listening to you, so let me provide you with a little more background and details. Firstly, this was not at all a closed door decision. We do ample user testing, have multiple avenues of collecting feedback, and in order to create this experience, first tested a number of different designs to see which one customers Liked the most Found easiest to use Resulted in the least accidental damage (such as from accidentally deleting someone else's work). Secondly, while the ability to cancel your changes has existed for a very long time in various text editors, these are in an environment where concurrent editing is not possible. If a number of people are editing something simultaneously, as with Google Docs, you have a revision history, but you can't remove just your edits. This is because of the nature of collaborative editing - if two people are writing something together, and each makes changes to what the other has written, should 'remove all my changes' remove what the other person has also done? Will it bring back what was changed? Will it delete the other person's work, if they wrote over yours? It's not a simple matter. Lastly, while it seems like we might be ignoring you, I assure you that our team reads every piece of feedback we receive and we thank you for taking the time to provide it. Thanks, Phil

            W.Erber added a comment -

            I don't understand why - instead of bringing back the previous simple cancel method - every suggestion to improve the current situation seems to make it more complicated.

            Granted, the old method was not without problems, but the new suggestions will introduce more problems by being far to complicated.

            A simple way to just exit without saving is probably a universal expectation with respect to text editors. It is unlikely that this will change soon - so any of the currently proposed solutions will annoy and confuse users.

             

            W.Erber added a comment - I don't understand why - instead of bringing back the previous simple cancel method - every suggestion to improve the current situation seems to make it more complicated. Granted, the old method was not without problems, but the new suggestions will introduce more problems by being far to complicated. A simple way to just exit without saving is probably a universal expectation with respect to text editors. It is unlikely that this will change soon - so any of the currently proposed solutions will annoy and confuse users.  

            This is the most ridiculous feature I have ever seen.  I agree with the comment above about releasing changes like this to clients to get feedback.  

            Rich Christy (x213) added a comment - This is the most ridiculous feature I have ever seen.  I agree with the comment above about releasing changes like this to clients to get feedback.  

            I agree that a "Cancel [only] my changes" option should be available. CTRL + Z in a browser is not reliable and not friendly to most [of our] users.

            Jonathan Hult added a comment - I agree that a "Cancel [only]  my changes" option should be available. CTRL + Z in a browser is not reliable and not friendly to most [of our] users.

            Atlassian team, for future enhancements, it would be good to create a test environment, and invite actual customers for usability testing. Release only those features that find wide acceptance. Closed room decisions do not work as the actual impacted parties are not consulted about their preferences.

            Ritu Sachdeva added a comment - Atlassian team, for future enhancements, it would be good to create a test environment, and invite actual customers for usability testing. Release only those features that find wide acceptance. Closed room decisions do not work as the actual impacted parties are not consulted about their preferences.

              poye philoye
              rgee Richie Gee (Inactive)
              Votes:
              153 Vote for this issue
              Watchers:
              86 Start watching this issue

                Created:
                Updated:
                Resolved: