97239efeef31 

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?:

Sorry to report that almost nothing is solved.

• Swimlane filters are still unusable as they show UUIDS
• 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 think it may be the same in other places, like quick filters etc., I did not perform the full QA of Jira fields.

Not sure why this ticket was closed despite these issues being mentioned in several comments. Maybe, there is another issue (or ten) for this particular bug, but no link(s) were provided, either. I must say I have little hope at this point, four years later, but I thought I should leave at least a comment about it.

Hey 298add8771bf I believe we would need a separate feature request for the different search input ("queues filter") you are referring to.

I had a similar conversation here and created this feature request for the search input that appears in Jira Software projects' quick filter settings: 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 am from the Jira Software (not Jira Service Management) support team so this is not my area of expertise, but the Jira Service Management Support team should be able to assist with creating such a ticket on your behalf.

Hi there,

the new issue search's feature seem to only be available in the advanced issue search. I'd like to reference https://support.atlassian.com/requests/PCS-276542/

To be precise, there are other places where this feature is not available yet. In my case it is Jira Service Management queues filter. My customer has several queue filters which involve specific users to exclude. At the moment the accountid is shown. Consider bringing this functionality to all places where JQL can be entered, e.g. JSM queues, JSW boards (quick-filters, colors,...) etc.

Hi everyone, as of yesterday all users should be able to access the "new issue search experience."

As the problem described in this ticket does not occur in the new issue navigator (see 15 February 2024 update in this ticket's Description), I'd like to tentatively suggest that this ticket can be closed but will wait a week before performing any actions.

If you think that this ticket should remain open, please leave a comment stating why. Thank you!

When I contacted the support in August 2021, the problem was acknowledged: "Currently, it is not possible for JQL to fetch usernames or emails from the database".

All saved filters, including board filters show UUIDs. Swimlane filters show UUIDs. It is quite unusable.

Hey Daniel, unfortunately, I see that in my projects sometimes it shows the user's display name, but in many cases, it is still a UUID. And I have no idea what the difference is between these cases. For us it is a huge problem, as it makes all our filters useless, nobody can read them, check and edit them, as we can't understand who is included there and who is not.

Hey lalmeida@atlassian.com
NIN and the new JQLEditor will show the user's display name and avatar instead of a UUID. Internally it will still use a UUID

Here's a community post about the features in the new JQLEditor https://community.atlassian.com/t5/Jira-articles/Unlock-the-power-of-search-with-the-new-JQL-editor/ba-p/1750670

+1  Alexandre's comment especially since all boards are based on filters.  

The issue is not limited to the "auto complete" feature.

This is related to JRACLOUD-72401 which is for some reason closed as "Won't fix", and "usability improvements" were supposed to be coming for over a year now. In the meantime, all filters for boards have been looking like this for months:

Project = SW AND Assignee in (5a2972f54e565f43b0320771, 557058:9784a49f-d308-4d85-9d94-eb32d379d1d2, 5aa69d74d0c9c42eefada8ec) ORDER BY Rank ASC

This makes using Reporter or Assignee, or any other user type field useless in a saved filter, unless the JQL in that filter can be rendered in Basic mode.

The suggested workaround is not a suitable replacement because it does not allow for validation of the input. So, it is easy to mistype and end up with an incorrect JQL query which in turn can lead to an important impact on the team.