-
Bug
-
Resolution: Obsolete
-
Medium
-
7.2.1, 7.2.3, 7.7.0, 7.7.1, 7.2.4, 7.12.3
-
7.02
-
88
-
129
-
NOTE: This bug report is for JIRA Server. Using JIRA Cloud? See the corresponding bug report.
Hello everyone! After analyzing this bug request, we realized that:
- This request is covering a symptom that can happen in several different scenarios, with very different causes.
- For most of the reported issues in the comments, the actual bug you are experiencing the KB that should help you in getting a workaround/resolution is 'User exists but has no unique key mapping' / User 'xxx' has no unique key mapping / The JIRA server was contacted but has returned an error response which covers most of the currently valid scenarios.
With these findings, we will be closing the bug request for now and in case the KB does resolve your scenario, please reach out to our support team, for them to analyze and determine the next steps, as you may be experiencing a variation of the known scenarios, something different like a performance/network issue or a completely new bug that needs to be identified and reported, with its own detailed bug.
Best regards,
René Chiquete - JAC Champion.
Clicking the 'Assignee' drop down in JIRA Server throws the following error in the JIRA interface:
The JIRA server was contacted but has returned an error response. We are unsure of the result of this operation
Atlassian is currently working on a solution that will be applied to all impacted customers.
Current Workaround:
- When the error message appear, click OK and start typing the username
- is duplicated by
-
JRACLOUD-65608 Server returns an 'error response' when attempting to set an assignee when using the 'Create Ticket' modal
- Closed
-
JRACLOUD-65774 Error when choosing down arrow on Assignee field
- Closed
-
JRACLOUD-65958 Error finding assignable user matching some substring
- Closed
-
JRASERVER-44823 Error when clicking on "Assignee" drop-down
- Closed
-
JRASERVER-44833 Server Error Response When Reassigning Ticket
- Closed
- relates to
-
JRACLOUD-44835 Assign issue drop down in JIRA throws "The JIRA server was contacted but has returned an error response. We are unsure of the result of this operation"
- Closed
-
JRASERVER-63109 Jira displays an error when searching for a username that has been renamed from mixed case
- Closed
-
HOT-33170 Loading...
- mentioned in
-
Page Loading...