-
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 ] |
Issue search "all issues" that we must use all the time because the new search for some reason does not show ALL labels, but only some of them... still unusable, shows UUIDs.
Sorry I wasn't clear that you were referring to using the old search when you said "all issues". Can I double-check is this the label issue you were referring to?: JRACLOUD-83652 – New issue search results - Components/Labels/Fields with multiple values only show '+X' instead all values like the old issue search results.
Thank you very much for providing the links to the related issues!
I guess it is the old search I have issue in. I was under impression I enabled the new search because on some screens I do not have the choice any more, but yes, the screen there is an issue in is definitely the old search. As I said in my previous comment, I only use the old search because the new one does not show all labels, but just a short version like "Label One +5".
Hey 97239efeef31 this bug was closed because it is no longer reproducible in the new issue search navigator:
Other JQL fields (such as those that appear in swimlane and quick filter settings) are covered in separate tickets as different engineering teams own the different fields:
JRACLOUD-83504 – On the Quick Filter settings page JQL should refer to a readable user information e.g. user name / email instead of user ID
I've just created a new one for swimlanes: JSWCLOUD-27239 – On the swimlanes settings page JQL should refer to a readable user information e.g. user name / email instead of user ID
- Board filters are still unusable, idem
- Issue search "all issues" that we must use all the time because the new search for some reason does not show ALL labels, but only some of them... still unusable, shows UUIDs.
I can't reproduce this when using the new issue search - can you confirm you have it enabled?:
| 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 ] |
When you have the old search enabled, SOME screens show the new search regardless. In such screens, there is a button enigmatically called "Go to all issues" in the top right, next to "share" and "export issues" which allows you to go to the old search.
The issue you just referenced is indeed the one that prevents us from using the new search. Thanks