-
Bug
-
Resolution: Fixed
-
Medium
-
32
-
Severity 3 - Minor
-
21
-
Issue Summary
Where performing a JQL search using a user field, selecting a value from the auto-complete options will populate username.
In the case of newer users, for example those provisioned with SCIM this is a UUID and not human readable in a usable sence.
Steps to Reproduce
- Provision a new user with SCIM.
- Assign an issue to the new user.
- Search for this user using JQL and type the display name of the user
assignee = jira
- Then select this user from the autocomplete pop-up.
Expected Results
The best result would be that the auto populated value would be either display name.
Actual Results
The username is populated which going forward will be a UUID.
Notes
This is related to the work being done to facilitate: Say goodbye to usernames in Atlassian Cloud
Workaround
To workaround this avoid using the auto-complete option and type the users display name or email address in quotes like
assignee = "nero@jira.com"
assignee = "Nero Battlebeard Wolfgang"
- is related to
-
JRACLOUD-73966 JQL should refer to a readable user information e.g. user name / email instead of user ID
- Closed
-
- Closed
- is resolved by
-
- Closed
- relates to
-
-
- Closed
-
- was cloned as
-
- Gathering Interest
[JRACLOUD-72062] Using the auto complete for JQL search on a user populates the username value which can be a UUID
| Component/s | Original: Jira Issue Search - Frontend [ 53297 ] |
| Component/s | New: Issue - Search - Frontend only [ 77950 ] |
| Attachment | New: screenshot-4.png [ 464279 ] |
| Link | New: This issue was cloned as JRACLOUD-84823 [ JRACLOUD-84823 ] |
| Attachment | New: screenshot-3.png [ 464277 ] |
| Attachment | New: image-2024-09-26-10-11-03-182.png [ 464276 ] |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Gathering Impact [ 12072 ] | New: Closed [ 6 ] |
| UIS | Original: 20 | New: 21 |
| UIS | Original: 19 | New: 20 |
| UIS | Original: 18 | New: 19 |