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

Better error message when viewing an embedded calendar as an unprivileged user

XMLWordPrintable

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

      On our site's dashboard I have a calendar macro defined as:

      {calendar:id=8f564b4b-afed-4ceb-b206-2e426f595648,a80c628d-5155-40bc-8a55-0874fb77bf71}

      The result is something that looks like this:

      After using the new features from TEAMCAL-102 to restrict view access of one of those calendars, users who don't have view rights to that calendar now see a huge warning on our site:

      I believe the appropriate user experience would be to see no errors and no indication that there is a calendar that they do not have access to. I understand this has to be balanced with the requirement for editors to know if they fat-finger a calendar id in their macros when editing, and the error is probably useful then. But big red boxes on dashboards are worse.

      Marking as critical because I believe this is a significant bug that will impact many users as they begin to utilize the new features from TEAMCAL-102.

        1. Embed Restrictions Message 01.png
          34 kB
          Samantha Thebridge [Atlassian]
        2. Embed Restrictions Message 02.png
          5 kB
          Samantha Thebridge [Atlassian]
        3. User without View Rights.JPEG
          126 kB
          Justin Clarke
        4. User with View Rights.JPEG
          63 kB
          Justin Clarke

            [CONFSERVER-51101] Better error message when viewing an embedded calendar as an unprivileged user

            Sen made changes -
            Workflow Original: JAC Suggestion Workflow 4 [ 3566113 ] New: JAC Suggestion Workflow 3 [ 4332224 ]
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow 2 [ 3181442 ] New: JAC Suggestion Workflow 4 [ 3566113 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3036610 ] New: JAC Suggestion Workflow 2 [ 3181442 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2522839 ] New: JAC Suggestion Workflow [ 3036610 ]
            Rachel Lin (Inactive) made changes -
            Workflow Original: Confluence Workflow - Public Facing v3 [ 2299909 ] New: Confluence Workflow - Public Facing v4 [ 2522839 ]
            Katherine Yabut made changes -
            Workflow Original: Confluence Workflow - Public Facing v3 - TEMP [ 2196344 ] New: Confluence Workflow - Public Facing v3 [ 2299909 ]
            Katherine Yabut made changes -
            Workflow Original: Confluence Workflow - Public Facing v3 [ 1949498 ] New: Confluence Workflow - Public Facing v3 - TEMP [ 2196344 ]
            Katherine Yabut made changes -
            Workflow Original: Confluence Workflow - Public Facing v2 [ 1756605 ] New: Confluence Workflow - Public Facing v3 [ 1949498 ]
            jonah (Inactive) made changes -
            Description Original: On our site's dashboard I have a calendar macro defined as:

            {code}{calendar:id=8f564b4b-afed-4ceb-b206-2e426f595648,a80c628d-5155-40bc-8a55-0874fb77bf71}{code}

            The result is something that looks like this:
            !User with View Rights.JPEG!

            After using the new features from TEAMCAL-102 to restrict view access of one of those calendars, users who don't have view rights to that calendar now see a huge warning on our site:
            !User without View Rights.JPEG!

            I believe the appropriate user experience would be to see no errors and no indication that there is a calendar that they do not have access to. I understand this has to be balanced with the requirement for editors to know if they fat-finger a calendar id in their macros when editing, and the error is probably useful then. But big red boxes on dashboards are worse.

            Marking as critical because I believe this is a significant bug that will impact many users as they begin to utilize the new features from TEAMCAL-102.             		New: {panel:bgColor=#e7f4fa}
              *NOTE:* This suggestion is for *Confluence Server*. Using *Confluence Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/CONFCLOUD-51101].
              {panel}

            On our site's dashboard I have a calendar macro defined as:

            {code}{calendar:id=8f564b4b-afed-4ceb-b206-2e426f595648,a80c628d-5155-40bc-8a55-0874fb77bf71}{code}

            The result is something that looks like this:
            !User with View Rights.JPEG!

            After using the new features from TEAMCAL-102 to restrict view access of one of those calendars, users who don't have view rights to that calendar now see a huge warning on our site:
            !User without View Rights.JPEG!

            I believe the appropriate user experience would be to see no errors and no indication that there is a calendar that they do not have access to. I understand this has to be balanced with the requirement for editors to know if they fat-finger a calendar id in their macros when editing, and the error is probably useful then. But big red boxes on dashboards are worse.

            Marking as critical because I believe this is a significant bug that will impact many users as they begin to utilize the new features from TEAMCAL-102.
            jonah (Inactive) made changes -
            Link New: This issue relates to CONFCLOUD-51101 [ CONFCLOUD-51101 ]

              merickson Matthew Erickson
              c15e2bcd81f1 Justin Clarke
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: