-
Suggestion
-
Resolution: Timed out
-
0
-
2
-
NOTE: This suggestion is for JIRA Portfolio Cloud. Using JIRA Portfolio Server? 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
- Create 2 groups - read-only and portfolio-editor.
- Grant read-only group with Portfolio Viewer permission in Portfolio global permission.
- Grant portfolio-editor group with Portfolio User permission in Portfolio global permission.
- Create 2 users - User A and User B.
- Put User A in read-only and User B in portfolio-editor.
- Create a Portfolio plan.
- Configure the plan's permission to give only User B for Viewers.
- Login with User A and try to access the plan. It is allowing this user to view it regardless of the plan's permission.
- Add portfolio-editor group to plan's permission Editors.
- 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.
- is related to
-
JSWSERVER-24792 Rework the plan/global permission handling
- Gathering Interest
- relates to
-
JRACLOUD-88790 Limit user view of plans
- Closed
-
JRACLOUD-89151 Allow setting of plan-level permission during Plan creation wizard
- Closed
- mentioned in
-
Page Loading...