-
Suggestion
-
Resolution: Unresolved
-
None
-
0
-
1
-
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
Currently, these two permissions are combined within the one "Browse Projects" permission.
The double personality of this permission causes confusion to administrator users as it is not obvious how the issue-specific values for these permissions ("security types" in JIRA code-speak) should behave in the project meaning of those permissions.
Examples of these values are: "Current Assignee", "Current Reporter" ...
mlassau has agreed to provide architectural advice and technical review for this work.
mlassau Could you please add initial design/implementation notes for aglowacki here?
Thanks mate.
CC: vosipov
- causes
-
JRASERVER-29840 User Picker field affecting the Browser Project permission
-
- Gathering Impact
-
- details
-
JRASERVER-37462 Create VIEW_ISSUE and BROWSE_PROJECT permissions
-
- Needs Triage
-
-
JRASERVER-37463 UpgradeTask - replace BROWSE permission with new ones
-
- Needs Triage
-
-
JRASERVER-37464 Replace all usages of BROWSE permission in JIRA code base
-
- Needs Triage
-
- relates to
-
JRACLOUD-37057 As an administrator, I would like to be able to grant permissions to browse projects and to browse issues independently
- Closed
- was cloned as
-
JDEV-33274 Loading...
Form Name |
---|
Isn't this what Issue Security is for?
Or am I missing some critical context here?