-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
3.8.2, 4.0.0, 4.4.0, 4.2.4
-
21
-
Severity 3 - Minor
-
3
-
Steps to Reproduce
- Have service Desk with either public sign up or any users that exist in JIRA
- Give a group jira administrator global permissions but not application access
- Assign an existing user that group
Expected Results
The customer will be able to view the Service Desk Portal
Actual Results
The customer no longer has access to the Service Desk Portal.
Also, the following symptoms are observed:
- When accessing the mail Help Center link, the following error is shown in the UI:
It looks like you don't have access to this help center. If possible, please try contacting us another way.
- When sending an email to the Service Desk Mail Handler to create an issue, the following error is found in the Mail logs:
You don't have permission to access this Service Desk.
- If the user has not logged yet into Jira and tries to log into the Customer Portal, the login will fail with the following error:
You do not have a permission to log in. If you think this is incorrect, please contact your Jira administrators.
Notes
This is especially susceptible when bringing in groups with LDAP and for the most part want the group to have admin access but some may not have application access.
Workaround
- Remove the user from the group
- Give the customer application access
- is related to
-
JSDCLOUD-11895 When a customer has administrator level permissions but no Jira access, they are not able to view any portals
-
- Closed
-
- links to
Form Name |
---|
We are using 4.13.3, having gone live with Jira Service Desk 2 weeks ago, and are running into this same issue. With 12-15 people in admin roles, granting them allocations from our 10 seats is absolutely not an option to work around this bug, as our team requires the seats already procured and allocated.
This bug is preventing leadership and managers with higher access from being able to submit any issues through the portal...absolutely not low priority for us given there does not seem to be a workaround that doesn't require procurement of additional licenses for users who are not working within the service desk software.