• 1
    • 7
    • We collect Jira 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 JIRA Portfolio Server. Using JIRA Portfolio Cloud? See the corresponding suggestion.

      Summary

      The current implementation of the permission handling can lead to some confusing scenarios where e.g. plan permissions get bypassed by global permissions.

      The interaction of these two permission levels should be redesigned.

      Scenario

      1. Create 2 groups - read-only and portfolio-editor.
      2. Grant read-only group with Portfolio Viewer permission in Portfolio global permission.
      3. Grant portfolio-editor group with Portfolio User permission in Portfolio global permission.
      4. Create 2 users - User A and User B.
      5. Put User A in read-only and User B in portfolio-editor.
      6. Create a Portfolio plan.
      7. Configure the plan's permission to give only User B for Viewers.
      8. Login with User A and try to access the plan. It is allowing this user to view it regardless of the plan's permission.
      9. Add portfolio-editor group to plan's permission Editors.
      10. Now, User A will be blocked from accessing the plan.

      Expected Behavior

      Portfolio should only allow User B to access the plan without the need of setting a group for Editors to enforce the permission.

            [JSWSERVER-24792] Rework the plan/global permission handling

            Marc Dacanay made changes -
            Labels Original: DC-150 Plan-Permiss affects-server jpos_1028 New: DC-150 Plan-Permiss affects-server jpos_1028 ril
            Marc Dacanay made changes -
            Remote Link New: This issue links to "Internal ticket (Web Link)" [ 979414 ]
            SET Analytics Bot made changes -
            UIS Original: 2 New: 1
            SET Analytics Bot made changes -
            UIS Original: 0 New: 2
            Aakrity Tibrewal made changes -
            Component/s New: (Advanced Roadmaps) Permissions [ 73713 ]
            Key Original: JPOSERVER-1220 New: JSWSERVER-24792
            Affects Version/s Original: 2.1.5 [ 64745 ]
            Project Original: Advanced Roadmaps [ 16510 ] New: Jira Software Server and Data Center [ 12200 ]
            Stasiu made changes -
            Labels Original: DC-150 affects-server jpos_1028 New: DC-150 Plan-Permiss affects-server jpos_1028
            Andrzej Kotas made changes -
            Labels Original: affects-server jpos_1028 New: DC-150 affects-server jpos_1028
            SET Analytics Bot made changes -
            UIS Original: 62 New: 0
            SET Analytics Bot made changes -
            UIS Original: 68 New: 62
            SET Analytics Bot made changes -
            UIS Original: 69 New: 68

              Unassigned Unassigned
              msturm@atlassian.com Martin Sturm (Inactive)
              Votes:
              8 Vote for this issue
              Watchers:
              12 Start watching this issue

                Created:
                Updated: