Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-21639

irregular editor behavior when it comes to unsaved changes

    • Icon: Suggestion Suggestion
    • Resolution: Duplicate
    • None
    • None
    • 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.

      When there are unsaved changes and I navigate away from the page editor, I am presented with a proper dialog box warning me about abandoning unsaved changes. Good.

      When I accidentally hit the cancel button (which is right next to the save button) I am not presented with a dialog box about discarding unsaved changes. Bad.

      Note: I am aware that in the past there has been a deliberate decisions about this inconsistent behavior (see JRA-23284 or CONF-7526) where things like this: (amount of annoyance of a confirm dialog) x (number of times people cancel deliberately) > (amout of annoyance of losing an edit) x (number of times people press cancel by mistake)
      are given as an argument.

      I'll restate my comment to that discussion:

      Here's what any other piece of software I have ever used in the last 20 years does:

      • You make edits to a document
      • You select File > Close, which is equivalent to the cancel button being discussed here
        IF there are unsaved changes, you are asked if you would like to save them or not.
        IF there are no unsaved changes, the file closes without further question.

      I am in the process of convincing about 50 reluctant co-workers to put their faith in confluence as the new way for our company to store and share information. Everyone is busy and reluctant to learn yet another piece of software. If they start losing data (like I just lost an hour of work) due to inconsistent and basically non standard functioning of the editor, then I am going to have a very difficult time indeed.

      If you still feel strongly about not making the change, then perhaps you can take it up with microsoft apple, and adobe to remove all of their warning dialogs when unsaved files are closed. Then at least my colleagues won't find a good reason to shun confluence over their old ways of squirreling away word document in dark and distant places all over our internal network.

      Thanks.

            [CONFSERVER-21639] irregular editor behavior when it comes to unsaved changes

            Michael S added a comment -

            Closing this as a duplicate of original issue CONF-7526, which has been re-opened.

            Michael S added a comment - Closing this as a duplicate of original issue CONF-7526 , which has been re-opened.

            Hi Maarten,

            I have created a JIRA support ticket for you at: support.atlassian.com You should receive an email shortly containing a direct link to the support ticket.

            Please refer to the support ticket for any future correspondence relating to this issue.

            In future can you please raise support requests such as this by creating an issue in our support system, https://support.atlassian.com, not in http://jira.atlassian.com. As our support engineers respond to cases in https://support.atlassian.com, it will ensure that your problem gets addressed as quickly as possible. Also, https://support.atlassian.com is configured so that only Atlassian and you have access to the case, therefore it is a more appropriate location for us to gather any required system data and configuration from you.

            Regards

            Atlassian Support Team.

            Patrick Gisbey added a comment - Hi Maarten, I have created a JIRA support ticket for you at: support.atlassian.com You should receive an email shortly containing a direct link to the support ticket. Please refer to the support ticket for any future correspondence relating to this issue. In future can you please raise support requests such as this by creating an issue in our support system, https://support.atlassian.com , not in http://jira.atlassian.com . As our support engineers respond to cases in https://support.atlassian.com , it will ensure that your problem gets addressed as quickly as possible. Also, https://support.atlassian.com is configured so that only Atlassian and you have access to the case, therefore it is a more appropriate location for us to gather any required system data and configuration from you. Regards Atlassian Support Team.

              mseager Michael S
              eb04f5923310 maarten rutgers
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: