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

Change "Save and Close" to "Save Draft and Close"

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Fixed
    • None
    • None

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

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

      A recent update to Confluence changed the way pages are saved/published after editing.  There are now two buttons: "Update" and "Save and Close".  It's not immediately apparent what these do.

      My first guess was that "Update" would incorporate any changes published by my colleagues into the draft I'm currently working on.  Instead "Update" actually publishes the draft that you're currently working on.  Thus, the "Update" button would more clearly communicate its purpose with the text "Publish".

      My first guess for the "Save and Close" button was that it would publish the draft I'm currently working on and return me to viewing the page.  This is similar to how Confluence previously worked.  Instead, this button saves the current draft and returns to viewing the current published version of the page.  This has confused some of my colleagues as well who frantically state that Confluence just lost all their work!  Instead of "Save and Close", this button should read "Save Draft and Close" (without the emphasis of course).

      These changes would really help people understand what the buttons do and prevent literally hours of frustration from people re-creating all their work that is already available in a draft!

            [CONFCLOUD-52115] Change "Save and Close" to "Save Draft and Close"

            Kevin Cannon added a comment -

            Thanks for the change, this has addressed the worst issue.

             

            However, "close" is still ambigious naming for this feature since it seems to:

            • Save a draft
            • Other people can access that draft and see the content
            • Other people can publish those unseen changes.

            Close could easily also be interpretted as:

            • Close and publish (why should a user have to read the Publish button to understand the difference?
            • Close without saving changes.

            It means "Save Draft" or similar.

            Trying to get our stakeholders to use confluence is hard enough without stuff like this.

            This is not a difficult problem. The world has solved this one already. No need to beat around the bush on this one.

            Kevin Cannon added a comment - Thanks for the change, this has addressed the worst issue.   However, "close" is still ambigious naming for this feature since it seems to: Save a draft Other people can access that draft and see the content Other people can publish those unseen changes. Close could easily also be interpretted as: Close and publish (why should a user have to read the Publish button to understand the difference? Close without saving changes. It means "Save Draft" or similar. Trying to get our stakeholders to use confluence is hard enough without stuff like this. This is not a difficult problem. The world has solved this one already. No need to beat around the bush on this one.

            Andrew Ashbacher added a comment -

            Thanks Phil!  I appreciate your team's quick response on this.

            Andrew Ashbacher added a comment - Thanks Phil!  I appreciate your team's quick response on this.

            philoye added a comment -

            We have changed the buttons labels to more clearly communicate their behavior.

            The buttons now read:

            • “Publish” - Updates the page
            • “Close” - Exits the editor without publishing your changes. Your edits are preserved and will be there the next time you edit the page.

            Thank you for all your feedback (and patience!) about this issue.

            philoye added a comment - We have changed the buttons labels to more clearly communicate their behavior. The buttons now read: “Publish”  - Updates the page “Close” - Exits the editor without publishing your changes. Your edits are preserved and will be there the next time you edit the page. Thank you for all your feedback (and patience!) about this issue.

            Kevin Cannon added a comment -

            This is terrible labelling. Causing loads of problems with our team.

            Should be something like "Publish" and "Save draft".

             

            Very poor UX decision. This should not have shipped!

            Kevin Cannon added a comment - This is terrible labelling. Causing loads of problems with our team. Should be something like "Publish" and "Save draft".   Very poor UX decision. This should not have shipped!

            Denny D Daugherty added a comment -

            This change has caused significant confusion to our users, and it is made worse by the lack of clear communication or documentation regarding such a significant change.

            Denny D Daugherty added a comment - This change has caused significant confusion to our users, and it is made worse by the lack of clear communication or documentation regarding such a significant change.

            Bill Latham added a comment - - edited

            This is at best "clunky" – we've had numerous cases where people think they are publishing their document because they clicked Save, only to find that the file they attached is invisible (until someone goes in and clicks Update).

            Update implies a Save.  Neither the words Update nor Save seems to imply the concept of "Publish" successfully.  Save Draft and Close would at least warn people that their changes wouldn't be visible (provided they understand what a "draft" is).

            All that being said, it shouldn't be this hard...

             

            Bill Latham added a comment - - edited This is at best "clunky" – we've had numerous cases where people think they are publishing their document because they clicked Save, only to find that the file they attached is invisible (until someone goes in and clicks Update). Update implies a Save.  Neither the words Update nor Save seems to imply the concept of "Publish" successfully.  Save Draft and Close would at least warn people that their changes wouldn't be visible (provided they understand what a "draft" is). All that being said, it shouldn't be this hard...  

            it_master_account added a comment -

            I tend to agree that the new naming is a bit clumsy. Also I am not very convinced about the way this has been implemented altogether. It feels like a lot of trouble just to edit documents. I am trying to convince our business (about 100 potential users) to move from Google Docs to Confluence and so far the document editing has been the center of the attention / discussions - and not for the good reasons.

            it_master_account added a comment - I tend to agree that the new naming is a bit clumsy. Also I am not very convinced about the way this has been implemented altogether. It feels like a lot of trouble just to edit documents. I am trying to convince our business (about 100 potential users) to move from Google Docs to Confluence and so far the document editing has been the center of the attention / discussions - and not for the good reasons.

              Unassigned Unassigned
              eb43ff7c5576 Andrew Ashbacher
              Votes:
              17 Vote for this issue
              Watchers:
              10 Start watching this issue

                Created:
                Updated:
                Resolved: