users can still view the Strategy snapshot despite all enterprise permissions have been turned off.

XMLWordPrintable

      Issue Summary

      In the 10.131 release, we can see the announcement:

      The strategic snapshot selection will be removed from the enterprise menu. Clicking enterprise will open the strategy room as it does today, but the snapshot selection will now be an in-page filter (as well as on the strategic backlog and strategy tree).
      The strategic snapshot filter in the sidebar menu will be replaced with the release filter (which already exists in the sidebar menu). This will allow you to filter for global views in the backlog and roadmaps.
      This means you will not need to grant additional permissions related to strategic snapshots to use the enterprise pages.

      In this version, upon testing we discover that all enterprise permissions on a specific (Enterprise Executive) role have been turned off. However, users can still view the Strategy snapshot.

      Steps to Reproduce

      1. in a test role, remove all enterprise permission
      2. login as a user who has this test role
      3. Go to enterprise section
      4. Notice that the snapshot dropdown is available and user has access to all snapshots, based on the PI they are members via their team assignment

      Expected Results

      As snapshot and all enterprise permissions are turned off, the user should not have access to the snapshot dropdown

      Actual Results

      snapshot dropdown is available and user has access to all snapshots, based on the PI they are members via their team assignment

      As a result, users can also access the strategy room for the snapshot they can select

      Workaround

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

            Assignee:
            Don Fuller
            Reporter:
            Erwann (Inactive)
            Votes:
            2 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: