-
Type:
Bug
-
Resolution: Won't Fix
-
Priority:
Low
-
Component/s: Integration - Identity
-
None
-
2
-
Severity 3 - Minor
Issue Summary
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>)
Steps to Reproduce
- Go to Jira search (advanced)
- Build a JQL referencing to existing users that has UUID as a username.
- Check the JQL that was generated.
Expected Results
The JQL should reference to a readable user information.
ie.
assignee in (<email_address1>, <email_address2>)
assignee in (<display_name1>, <display_name2>)
Actual Results
assignee in (<UUID1>, <UUID2>)
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.