[JRACLOUD-37057] As an administrator, I would like to be able to grant permissions to browse projects and to browse issues independently - Create and track feature requests for Atlassian products.

Type: Suggestion
Resolution: Low Engagement
Component/s: Permissions - Configuring People, Roles and Permissions
Labels:

UIS:
0
Support reference count:
7
Feedback Policy:

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.

NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? 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

is caused by

JRACLOUD-31720 Grant "Browse Project" permission to "Current Assignee" makes project visible to all users

Closed

is related to

JRASERVER-37057 As an administrator, I would like to be able to grant permissions to browse projects and to browse issues independently

Gathering Interest

1.	Create VIEW_ISSUE and BROWSE_PROJECT permissions	Closed	Unassigned
2.	UpgradeTask - replace BROWSE permission with new ones	Closed	Unassigned
3.	Replace all usages of BROWSE permission in JIRA code base	Closed	Unassigned

Loading...

Type: Suggestion
Resolution: Low Engagement
Component/s: Permissions - Configuring People, Roles and Permissions
Labels:

UIS:
0
Support reference count:
7
Feedback Policy:

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.