Filter returning results for all but one project

Question

Hello, I'm running into a recurring filter failure with one project. Here are the details:

Filter:

assignee = [employee ID here] AND status != Done OR Sub-Assignee = [employee ID here] AND status != Done

Failure:

The above filter successfully pulls results from all but one project. We have an even mix of classic and next-gen projects. The one in question (ie no results returned from the filter) is a next-gen project, with identical accesses (users and groups) as other next-gen projects that return results as expected. Thought's or recommendations appreciated.

liam_8zqazm · Answer

By addressing your earlier recommendation regarding the "Sub-Assignee" shared custom field, via "Sub-Assignee(s)" (quotes included) in combination with both assignee and Sub-Assignee as provided above (inside parenthesis), I get all expected project data from the filter. Worth noting that when I initially replaced Sub-Assignee with "Sub-Assignee(s)", I actually lost results from other projects.

Regardless, I have a comprehensive working filter for our company dashboards. Really appreciate your help Jack. 10/10.

Jack Brickey · Answer

Sorry if I misdirected you previously. If you want to find all issues that are 'not done' with the assignee or sub-assignee being a certain user then include  parenthesis so that the assignee fields are first assessed ....

(Assignee = user-xxx or sub-assignee = user-xxx) AND status != Done

If this is to be a filter used by any individual to see any work assigned or sub-assigned the them that they have not completed then use "currentuser()" in place of any specific user in the above JQL.

Something else to consider here:

* if you have other statuses that equate to an issue being complete, e.g. resolved, cancelled, etc. then consider using statuscategory != done instead of status

liam_8zqazm · Answer

Jack, thank you for the quick reply. I ran the query as you have it above in initial filter testing, and I just ran it again to verify the result: employee results with a status of "Done" are returned. It appears that (my assumption during initial testing) this is due to assignee = [employee ID here] followed by "OR" returns anything that the employee has been assigned to, ignoring the "AND" logic with the status qualification "!= Done". Happy to test anything else you think might help.