-
Bug
-
Resolution: Duplicate
-
Low (View bug fix roadmap)
-
None
-
None
NOTE: This bug report is for JIRA Server. Using JIRA Cloud? See the corresponding bug report.
I have a JQL search which is supposed to return all issues which I am watching but not the assignee or reporter. The original search I wrote is:
status != closed and watcher = "myusername" and reporter != "myusername" and assignee != "myusername"
However, it appears that the parameter "assignee != "myusername" " does not return issues that are completely unassigned, which means I had to alter the search to be:
resolution = EMPTY and watcher = "myusername" and reporter != "myusername" and (assignee != "myusername" or assignee is empty).
This seems like bad logic to me; if an issue is unassigned, its by definition not assigned to me. Can this be fixed?
- duplicates
-
JRASERVER-35103 Include "Unassigned" issues, when searching for "assignee not in (userlist)"
- Closed
- relates to
-
-
- Closed
-
[JRASERVER-36767] Unassigned Users Not Being Returned When Searching for Issues Not Assigned to Specific User
| Workflow | Original: JAC Bug Workflow v2 [ 2844385 ] | New: JAC Bug Workflow v3 [ 2927643 ] |
| Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
| Workflow | Original: JIRA Bug Workflow w Kanban v7 - Restricted [ 2581894 ] | New: JAC Bug Workflow v2 [ 2844385 ] |
| Workflow | Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 1533672 ] | New: JIRA Bug Workflow w Kanban v7 - Restricted [ 2581894 ] |
| Description |
Original:
I have a JQL search which is supposed to return all issues which I am watching but not the assignee or reporter. The original search I wrote is:
status != closed and watcher = "myusername" and reporter != "myusername" and assignee != "myusername" However, it appears that the parameter "assignee != "myusername" " does not return issues that are completely unassigned, which means I had to alter the search to be: resolution = EMPTY and watcher = "myusername" and reporter != "myusername" and (assignee != "myusername" or assignee is empty). This seems like bad logic to me; if an issue is unassigned, its by definition not assigned to me. Can this be fixed? |
New:
{panel:bgColor=#e7f4fa} *NOTE:* This bug report is for *JIRA Server*. Using *JIRA Cloud*? [See the corresponding bug report|http://jira.atlassian.com/browse/JRACLOUD-36767]. {panel} I have a JQL search which is supposed to return all issues which I am watching but not the assignee or reporter. The original search I wrote is: status != closed and watcher = "myusername" and reporter != "myusername" and assignee != "myusername" However, it appears that the parameter "assignee != "myusername" " does not return issues that are completely unassigned, which means I had to alter the search to be: resolution = EMPTY and watcher = "myusername" and reporter != "myusername" and (assignee != "myusername" or assignee is empty). This seems like bad logic to me; if an issue is unassigned, its by definition not assigned to me. Can this be fixed? |
| Link |
New:
This issue relates to |
| Component/s | New: Issue Navigation & Search - JQL [ 43398 ] | |
| Component/s | Original: JQL [Deprecated] [ 12922 ] | |
| Labels | New: ho-jql-backend |
| Workflow | Original: JIRA Bug Workflow w Kanban v6 [ 665435 ] | New: JIRA Bug Workflow w Kanban v6 - Restricted [ 1533672 ] |
| Workflow | Original: JIRA Bug Workflow w Kanban v5 [ 642470 ] | New: JIRA Bug Workflow w Kanban v6 [ 665435 ] |
| Workflow | Original: JIRA Bug Workflow w Kanban v5 [ 621121 ] | New: JIRA Bug Workflow w Kanban v6 [ 642470 ] |
| Component/s | New: JQL [ 12922 ] |
