Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-36767

Unassigned Users Not Being Returned When Searching for Issues Not Assigned to Specific User

      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?

            [JRASERVER-36767] Unassigned Users Not Being Returned When Searching for Issues Not Assigned to Specific User

            Hi haddon.fisher,

            Thanks for reaching out to us.

            The behaviour you have noticed whilst not intuitive is part of how JQL search is designed to work. Please also see https://jira.atlassian.com/browse/JRA-35103 which is a duplicate of this same behaviour.

            Regards,

            Oswaldo Hernández.
            JIRA Bugmaster.
            [Atlassian].

            Oswaldo Hernandez (Inactive) added a comment - Hi haddon.fisher , Thanks for reaching out to us. The behaviour you have noticed whilst not intuitive is part of how JQL search is designed to work. Please also see https://jira.atlassian.com/browse/JRA-35103 which is a duplicate of this same behaviour. Regards, Oswaldo Hernández. JIRA Bugmaster. [Atlassian] .

              Unassigned Unassigned
              8ddfbafaefcc Haddon Fisher
              Affected customers:
              1 This affects my team
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: