-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
4.4.5, 5.2, 7.3.3
-
4.04
-
3
-
Severity 3 - Minor
-
0
-
Hi,
I was looking a customer issue (JSP-122240) and discover a bug on JIRA.
How to replicate:
- Create a clean JIRA instance;
- create two users (Administrator - login admin / User 1 - login user)
- Create a new project (e.g. Project X - PX);
- Create 4 issues (PX-1, PX-2, PX-3, PX-4);
- Assign one issue (PX-2) for the user User 1 and the others for the Administrator;
Try the following queries:
- project=PX AND assignee was "admin"
- response: 4 issues
- project=PX AND assignee = "admin"
- response: 3 issues
- project=PX AND assignee = "Administrator"
- response: 3 issues
- project=PX AND assignee was "Administrator"
- response: No matching issues found.
The last query supposed to bring 4 issues, like the first one, but looks like the operator WAS just work with the Username and not with the Full Name.
Cheers,
Andre Petry
Atlassian Support
- is duplicated by
-
JRASERVER-26953 'WAS' operator does not work with full names in advanced searching
- Closed
- relates to
-
JRASERVER-28091 Assignee history (WAS / CHANGED FROM) not searchable by either full name or user name when searching anonymously
- Gathering Impact
- links to