-
Bug
-
Resolution: Unresolved
-
Medium (View bug fix roadmap)
-
None
-
8.20.1, 8.13.14, 8.21.0, 8.20.3, 8.20.7, 9.4.1, 9.4.5
-
8.13
-
11
-
Severity 2 - Major
-
3
-
Issue Summary
Selecting a user for assignee in basic mode, below error will occur in search screen.
The Jira server could not be contacted. This may be a temporary glitch or the server may be down.
This problem only happen when current user does not have Browse Users global permission .
Steps to Reproduce
- Remove [Browse Users] permission for a group
- Login Jira with a user belong to the above group
- Move to Issues > Search for issues
- Click [Assignee], and enter a username.
- A user will show up, click the checkbox for the user
Expected Results
No error, and the clicked user from user search box will be selected in "Search for issues".
Actual Results
Blow error is shown in the page
The Jira server could not be contacted. This may be a temporary glitch or the server may be down.
Also, 403 error happened in har file for below request.
http://11.22.3344:8080/secure/QueryComponentRendererValue!Default.jspa
The clicked user from user search box won't be selected in "Search for issues".
Workaround
The ability to search against a known user still works in Advanced Mode using JQL. However, no known workaround exists for allowing this search in Basic Mode.
- is related to
-
-
- Gathering Impact
-
-
ENT-822 Failed to load
- relates to
-
JRASERVER-73355 When a user does not have the global permission to browse users they get an error that appears to be a system failure
- Gathering Interest
- mentioned in
-
Page Failed to load
-
Page Failed to load
-
Page Loading...
-
-
-
-
-
Atlassian has marked this as Low Priority and it remains unassigned. I would say it is higher than "low" for our organization. Please assign this issue to the technical team so that it can be addressed. This is clearly a bug in the code.