-
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
-
JRACLOUD-73982 Better JQL UI experience for customers in Issue Navigator when using "Reporter" or "Assignee"
- Closed
-
JRACLOUD-83029 JQL filters display accountID
- Closed
- is related to
-
JRACLOUD-74155 Consolidated search for Jira Cloud
- Closed
- is resolved by
-
JRACLOUD-74155 Consolidated search for Jira Cloud
- Closed
- is superseded by
-
JSWCLOUD-27239 On the swimlanes settings page JQL should display human-readable user information e.g. user name / email instead of user ID
- Gathering Impact
-
JSWCLOUD-26665 On the Quick Filter settings page JQL should refer to a readable user information e.g. user name / email instead of user ID
- Long Term Backlog
- relates to
-
JRACLOUD-72062 Using the auto complete for JQL search on a user populates the username value which can be a UUID
- Closed
-
JRACLOUD-76147 JQL search using WAS operator and BY predicates does not auto populate username or Account ID based on string
- Long Term Backlog
- was cloned as
-
JSWCLOUD-26665 On the Quick Filter settings page JQL should refer to a readable user information e.g. user name / email instead of user ID
- Long Term Backlog