-
Suggestion
-
Resolution: Duplicate
-
3
-
When a user lacks the browse users and groups global permission and attempts to create a user-based search they get the following error:
"The JIRA server was contacted but has returned an error response. We are unsure of the result of this operation."
Users should either get an error that they lack permission or better, should not have the basic search options for searching on a user at all.
Either way, THIS looks like a system failure. This error gets people calling the admin team, asking why Jira is failing.
- duplicates
-
JRACLOUD-74169 Unclear error when user without global "Browse users and groups" permission clicks Assignee in basic search
-
- Gathering Impact
-
- was cloned as
-
- Gathering Interest
[JRACLOUD-75183] When a user does not have the global permission to browse users they get an error that appears to be a system failure
| Component/s | Original: Jira Issue Search - Frontend [ 53297 ] |
| Component/s | New: Issue - Search - Frontend only [ 77950 ] |
| Resolution | New: Duplicate [ 3 ] | |
| Status | Original: Gathering Interest [ 11772 ] | New: Closed [ 6 ] |
| Attachment | New: screenshot-1.png [ 449602 ] |
| Labels | New: RIBS-Long |
| Component/s | Original: Global Administration - Project Roles, Permission Helper and Global Permissions [ 66291 ] | |
| Component/s | New: User search [ 72699 ] |
| Support reference count | Original: 2 | New: 3 |
| Component/s | New: Global Administration - Project Roles, Permission Helper and Global Permissions [ 66291 ] |
| Support reference count | Original: 1 | New: 2 |
After some analysis, we've found that this ticket is a duplicate of the request JRACLOUD-74169 – When some users attempt to find assignees in Jira basic mode search, an error is thrown: "The Jira server was contacted but has returned an error response. We are unsure of the result of this operation." which has more votes.
We encourage you to watch and vote on the above instead. All internal ticket references on this ticket have been transferred. If you do not think this issue should have been closed, please add a comment here saying why and we can reopen it.