Uploaded image for project: 'Jira Service Management Cloud'
  1. Jira Service Management Cloud
  2. JSDCLOUD-11906

Display a message when setting the same Group Viewer and Editor for a Dashboard

XMLWordPrintable

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

      Issue Summary

      No message is displayed when trying to select the same Group as Viewer and Editor in the Rename or Share menu for the Dashboard.

      The current behavior is that when you set Group "ABC" as Viewer, and then afterward try to set the same Group "ABC" as Editor, the "Viewer" Group is switched back to "Private".

      This might be due to the reason that when a Group is "Editor" it already inherits the "Viewer" permission role, but that might lead the user to think that it might be for some other reason - due to a bug, for example.

      So, we have this suggestion in place in order to inform the User exactly why the previously selected Group as "Viewer" was changed to "Private" when setting this Group also as "Editor".
       

      Steps to Reproduce

      1. Step 1 - Log into Jira and open a Dashboard
      2. Step 2 - In the "..." menu at top-right corner of page, select "Rename or Share"
      3. Step 3 - In the pop-up displayed, in the "Viewers" Section, select Group and pick a group from the list. Finally, hit "Add" so the Group is added to the Configuration.
      4. Step 4 - In the "Editors" section, select Group and pick the same Group selected in the step below. Try hitting "Add".

       

      Expected Results

      • Or a message being displayed telling that the Viewers Group changed because the Editors Group already has this permission;
      • Or the Group selected being added to the "Editors" Configuration alongside the "Viewers" Configuration;

      Actual Results

      The Viewers Group is cleared and its value is switched back to Private, and no message is displayed informing the User why that happened.

      Workaround

      Currently, there is no known workaround for this behavior. A workaround will be added here when available

              Unassigned Unassigned
              2cbc34056992 Michel Guedes
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: