-
Bug
-
Resolution: Unresolved
-
Low
-
14
-
Severity 3 - Minor
-
0
-
Steps to Reproduce
- In JSD project A, set the customer permission as "Who can access the portal and send requests to <project key>?": "Customers my team adds to the project"
- Confirm that the project has no customers added
- Edit the permission scheme to add "Browse Project" permission to "Reporter" or "custom user pick field"
- Access the portal by a customer that has access to customer portal(customer that is added to another project B)
Expected Results
Customer will only see project B
Actual Results
Customer sees both project A and B
Workaround
Remove "Reporter" or "custom user pick field" from "Browse Project" permission
- relates to
-
JRACLOUD-79840 Jira Permission schemes should not allow you to attempt to configure nonsensical permission states
- Closed
- was cloned as
-
JSDSERVER-12130 "Browse Project" permission set to specific values overrides the customer permission that results in the project getting exposed in the customer portal
- Closed