Details
-
Suggestion
-
Resolution: Unresolved
-
121
-
146
-
Description
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.
Attachments
Issue Links
- is duplicated by
-
- Closed
-
- Closed
- is related to
-
- Closed
- is resolved by
-
- Closed
- relates to
-
JRACLOUD-72062 Using the auto complete for JQL search on a user populates the username value which can be a UUID
-
- Gathering Impact
-
-
-
- Long Term Backlog
-
- was cloned as
-
- Gathering Interest