You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi there,
I'm trying to create a JQL filter inside one project, to filter all issues with an "empty" "assignee" AND with "assignee" "not in" (username, username).
But the following statement doesn't work:
project = "ABC" AND Sprint in (347, 331) AND assignee not in (username, username, username, username) AND assignee = EMPTY AND status not in (done, Storno) AND status not in (Done, Resolved) ORDER BY assignee ASC, cf[10004] ASC
What' wrong?
Thanks in advance.
You've defined a query that can not possibly return anything.
Just looking at the bit that causes the problem, and shortening it a bit), have a think through what this really says:
assignee not in (A, B, C, D) and assignee is empty
There's two possibilities there, the assignee is either filled with something, or it is empty. If you AND those, you're always going to get nothing because it cannot be both values at the same time.
I think your query should be:
project = "ABC" AND Sprint in (347, 331) AND
( assignee not in (username, username, username, username) OR assignee is EMPTY )
AND status not in (done, Storno, Done, Resolved)
ORDER BY assignee ASC, cf[10004] ASC
That was fast :)
Thank you very much and you're absolutely right, but sometimes you need a different person to check the work.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I know what you mean. JQL queries are one of the things I often need someone else to check!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Nic,
but... what I found today is that if you filter for a property not being something (and the property can be empty) then the filter will not match the empty ones.
for example:
assignee != UserName
will return less results than
assignee != UserName OR assignee is EMPTY
And this behaviour will also occur for labels , comments , etc.
labels != LabelName
labels != LabelName OR labels is EMPTY
Comment !~ "WordToExclude"
Comment !~ "WordToExclude" OR comments is EMPTY
Is this a bug on JIRA?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Does anyone know if Atlassian has something like an ISEMPTY(assignee, "") = "Jane Smith" in the works? Something that works like ISNULL or NVL in the SQL languages.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.