-
Suggestion
-
Resolution: Fixed
-
32
-
148
-
Hi everyone,
As of 2 April 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, below), 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!
Hi everyone,
The problem described in this ticket does not occur in the new issue navigator which we are aiming to roll out over the next few months. You can find more information here: JRACLOUD-74155 – Consolidated search for Jira Cloud
You can test out this functionality by going to any company-managed project > Issues:
Problem
As part of the efforts to remove username in Cloud, some users are already configured with a UUID as the username. When those users are referenced in a JQL query (assignee/reporter), the data user information is not readable.
ie.
assignee in (<UUID1>, <UUID2>)
Suggested Solution
The JQL should refer to readable user information.
ie.
assignee in (<email_address1>, <email_address2>)
assignee in (<display_name1>, <display_name2>)
Workaround
Run the JQL in Jira search and switch to Basic to retrieve the user information.
Run the JQL query and inspect the results to check for the user information.
- is duplicated by
-
- Closed
-
- Closed
- is related to
-
- Closed
- is resolved by
-
- Closed
- is superseded by
-
- Gathering Interest
-
- Gathering Interest
- relates to
-
JRACLOUD-72062 Using the auto complete for JQL search on a user populates the username value which can be a UUID
-
- Closed
-
-
-
- Long Term Backlog
-
- was cloned as
-
- Gathering Interest
[JRACLOUD-73966] JQL should refer to a readable user information e.g. user name / email instead of user ID
Hi e0f14316fa01 thanks for flagging this - I think the tickets you shared are all we have right now:
- JRACLOUD-78977 – Using the auto complete for JQL search on an Assets field converts the Assets field name value to non-readable ARI value
- JRACLOUD-81748 – Teams are not displaying as it should be with a minor ID for the team in JQL
Can I check, are there any elements of the feature you are after that are not yet covered in the above?
Hi Anusha,
Is there any other ticket for tracking user-readable information in JQL for the "Team" or "Assets objects" fields? These two still show up as IDs.
https://jira.atlassian.com/browse/JRACLOUD-81748, https://jira.atlassian.com/browse/JRACLOUD-74842, https://jira.atlassian.com/browse/JRACLOUD-78977
Thanks very much for confirming c8eab6a75592 I have created another ticket to track that issue, here: 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
Yes, this is the correct spot @Anusha Rutnam. If it's a different team, then a sep. ticket would be advisable
Hey c8eab6a75592 thanks for the feedback - can I confirm that you are referring to this view in Quick filters settings?:
(Screenshot is from company-managed Jira Software project with Scrum board > Configure board > Quick filters)
If so, I will create a new ticket for you because I think a different team owns that functionality.
I can confirm, that for us this fixed the problems in the Filter JQL dialog.
However, it is still partly visible in the configuration of Quick Filters in Boards (The saved JQL contains the UID, which is converted back if you edit the Quick Filter again). So you have to edit the filter first, to see which users are included. Not a big deal I guess, but different from the Filter JQL dialog
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!
Hi All,
Thank you for you patience on this issue. Readable user information is now shown in JQL on the Filters/Issue Navigator page.
Please vote on and watch the following tickets for specific fields:
Thanks,
Daniel