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

      From blitz test - a user unfamiliar with the Restrictions dialog found it confusing to use.

      There isn't much text on it at the moment - it assumes that users are familiar with the restrictions UI in previous versions.

      We sat together and went through the points of confusion, and suggested text that would make it more obvious how the dialog is supposed to be used. See attached.

      Update

      Summarizing the comments below the following changes should be made:

      • Revert the radio buttons to what they said before
      • Change the text of the entry field (we did have an old wording that used username&groupname)
      • Include a link to the documentation.

            [CONFSERVER-17515] Improve explanatory text on Page Restrictions dialog

            m@ (Inactive) added a comment - Reviewed: https://atlaseye.atlassian.com/cru/CR-CONF-456

            I updated the issue description to match the work that was actually requested. The work done broke into those three areas - radios, text-field placeholder and Help link.

            The first two changes only required changes to CSS/VM and CAS.props, while the third change needed a JavaScript change.

            David Taylor (Inactive) added a comment - I updated the issue description to match the work that was actually requested. The work done broke into those three areas - radios, text-field placeholder and Help link. The first two changes only required changes to CSS/VM and CAS.props, while the third change needed a JavaScript change.

            How about you do this with Ben so he learns more about how we do wording changes?

            Per Fragemann [Atlassian] added a comment - How about you do this with Ben so he learns more about how we do wording changes?

            Okay, had a chat with QA, and since Stephen agrees as well, it's a safer bet to keep the UI similar to what it was before (in case you don't remember, here's the old documentation: http://confluence.atlassian.com/display/CONF30/Setting+a+Page%27s+Restrictions)

            Let's do the things we find uncontroversial:

            • Revert the radiobuttons to what they said before
            • Change the text of the entryfield (we did have an old wording that used username&groupname)
            • If possible include a link to the documentation.

            However, let's keep the "To:", and let's not call it "add restriction", because it sounds like you would be adding something when actually you are restricting something.

            Per Fragemann [Atlassian] added a comment - Okay, had a chat with QA, and since Stephen agrees as well, it's a safer bet to keep the UI similar to what it was before (in case you don't remember, here's the old documentation: http://confluence.atlassian.com/display/CONF30/Setting+a+Page%27s+Restrictions ) Let's do the things we find uncontroversial: Revert the radiobuttons to what they said before Change the text of the entryfield (we did have an old wording that used username&groupname) If possible include a link to the documentation. However, let's keep the "To:", and let's not call it "add restriction", because it sounds like you would be adding something when actually you are restricting something.

            What we really need is a link from the dialog to the documentation. Then anyone who is confused can read all the details over there. Right now, I am fine with the dialog for most usecases. It is definitley better than before already.

            Per Fragemann [Atlassian] added a comment - What we really need is a link from the dialog to the documentation. Then anyone who is confused can read all the details over there. Right now, I am fine with the dialog for most usecases. It is definitley better than before already.

            • "Enter user name" versus "Enter user name or group name" - the problem with not mentioning that you can enter a group name means that most users will not know that you can, and therefore will not use it. It's actually a nice feature that you can just directly type group names, and shouldn't be hidden away, as users will otherwise assume they need to use the rather cumbersome "Group Search" popup window. There may be a better way to make this clear, of course.
            • "Restrict" versus "Add Restriction" - it wasn't clear to a user in the blitz test what to do on this screen, and what clicking on that button would mean. In fact, you would only need to click the button if you have entered a user name or group name, and want to add that into the list. If you use the Me/User/Group buttons instead, then you wouldn't ever need to click on the button. My suggestion was trying to make this point of confusion a bit clearer - again there may be a better way to do this.

            Mark Hrynczak (Inactive) added a comment - "Enter user name" versus "Enter user name or group name" - the problem with not mentioning that you can enter a group name means that most users will not know that you can, and therefore will not use it. It's actually a nice feature that you can just directly type group names, and shouldn't be hidden away, as users will otherwise assume they need to use the rather cumbersome "Group Search" popup window. There may be a better way to make this clear, of course. "Restrict" versus "Add Restriction" - it wasn't clear to a user in the blitz test what to do on this screen, and what clicking on that button would mean. In fact, you would only need to click the button if you have entered a user name or group name, and want to add that into the list. If you use the Me/User/Group buttons instead, then you wouldn't ever need to click on the button. My suggestion was trying to make this point of confusion a bit clearer - again there may be a better way to do this.

            This seems like fair feedback. This is actually how they were worded before.

            I would remove the label "Restrict:", left align the radio checkboxes, and change their labels to what Mark suggested.

            I'm less convinced by the other suggestions.

            • The "Enter user name" text was changed from what you suggested because autocomplete only works for user names. If we add "group name" to this description, people may think that the group doesn't exist when the drop down appears and groups are not displayed.
            • I don't see what problems the "Add Restriction" text solves? It seems to make it more technical in my mind...

            Stephen Russell [Atlassian] added a comment - This seems like fair feedback. This is actually how they were worded before. I would remove the label "Restrict:", left align the radio checkboxes, and change their labels to what Mark suggested. I'm less convinced by the other suggestions. The "Enter user name" text was changed from what you suggested because autocomplete only works for user names. If we add "group name" to this description, people may think that the group doesn't exist when the drop down appears and groups are not displayed. I don't see what problems the "Add Restriction" text solves? It seems to make it more technical in my mind...

            I suppose the dialog might expect a degree of familiarity with the Confluence restriction mechanism but I'm not sure I like your suggested improvements.

            For instance, the top line of the dialog would already read as:
            "Restrict Viewing, Restrict Editing" to anyone familiar with radio buttons.
            The other changes don't seem to add a lot, but i'll get some comments from others.

            Paul Curren added a comment - I suppose the dialog might expect a degree of familiarity with the Confluence restriction mechanism but I'm not sure I like your suggested improvements. For instance, the top line of the dialog would already read as: "Restrict Viewing, Restrict Editing" to anyone familiar with radio buttons. The other changes don't seem to add a lot, but i'll get some comments from others.

              dtaylor David Taylor (Inactive)
              mhrynczak Mark Hrynczak (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: