Filters: watchers where current user is not an assignee - returning incorrect results

I am attempting to create a filter that will show all tickets I am watching, but am not assigned to. I know that I am watching six tickets on my company's JIRA system, and I know I am assigned to only one of those tickets.

This Query works as expected:
watcher = currentUser() ORDER BY updatedDate DESC 
=> Results in six tickets

This Query Works as expected:
watcher = currentUser() AND assignee = currentUser() ORDER BY updatedDate DESC
=> Finds one ticket that I am watching and assigned to

This Query does not work:
watcher = currentUser() AND assignee != currentUser() ORDER BY updatedDate DESC
=> Finds ONE ticket, there are four missing tickets

I noticed there is one difference between the four tickets that were not found and the one ticket that was found. The ticket that was returned has a user assigned to it, all the other users are unassigned.


I have attempted these variations:
watcher = currentUser() AND assignee not in (currentUser()) ORDER BY updatedDate DESC
issue in watchedIssues() AND assignee not in (currentUser()) ORDER BY updatedDate DESC
issue in watchedIssues() AND assignee != currentUser() ORDER BY updatedDate DESC
issue in watchedIssues() AND NOT assignee = currentUser() ORDER BY updatedDate DESC

All of these variations give me the same results.

My company is currently using JIRA v6.3.1.

UPDATE:

I have tried this search too:

watcher = currentUser() AND assignee is EMPTY ORDER BY updatedDate DESC
=> Results in the four unassigned tickets
watcher = currentUser() AND assignee is EMPTY AND NOT assignee = currentUser() ORDER BY updatedDate DESC
=> No tickets

I think I am getting closer but it seams like I am still missing something.

3 answers

1 accepted

4 votes
Accepted answer

This seams to work, the comparator was the important piece that I was missing.

watcher = currentUser() AND (assignee is EMPTY OR assignee != currentUser()) ORDER BY updatedDate DESC

It seems like a bug that "assignee != currentUser()" does not cover assignee is EMPTY... logically if assignee is EMPTY, it's also != currentUser().

Agreed Dave H.  "assignee is EMPTY" shouldn't be necessary but at least the filter works correctly now.  Thanks ckdesigns!

if you think of EMPTY as NULL, it would make sense that NULL does not return as "not equal to" a value since there is nothign to compare. It's not uncommon in languages. 

Thank you! This is exactly what I was looking for! 

Thank you! This has been a great help!

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Feb 13, 2019 in Jira

Make your Atlassian Cloud products more secure: our NEW admin security guide

Hey admins! I’m Dave, Principal Product Manager here at Atlassian working on our cloud platform and security products. Cloud security is a moving target. As you adopt more products, employees consta...

605 views 0 12
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you