-
Bug
-
Resolution: Unresolved
-
Medium
-
1
-
Severity 3 - Minor
-
0
-
Issue Summary
When viewing a board's swimlane JQL query, users are referred to by UUID rather than username or email.
Steps to Reproduce
- In a company-managed Jira Software project go to Board configuration > Swimlanes and click Create swimlane
- Add a query that includes a reference to a specific user. Side note: in the Create swimlane modal the username does appear:
- Click Create and observe that the username no longer appears in the JQL query column of the swimlane list, with the UUID appearing instead:
Expected Results
Queries used in swimlanes should appear in a human-readable form when viewing swimlane settings.
Actual Results
Queries used in swimlanes contain UUID instead of human-readable name or email when viewing swimlane settings.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
Notes
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. This issue is fixed in the new issue search experience (see JRACLOUD-73966) but remains in Swimlanes settings.
- is cloned from
-
JRACLOUD-72062 Using the auto complete for JQL search on a user populates the username value which can be a UUID
- Closed
- is related to
-
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
- supersedes
-
JRACLOUD-73966 JQL should refer to a readable user information e.g. user name / email instead of user ID
- Closed