Trust Your JQLs - Vote for fix

[Normann P_ Nielsen _Netic_]

I just found out recently, that a filter did not show many issues as espected.

This costed my company some grief and me a log of explaning and support, both internal and towards Atlassian.

Bug Report: https://jira.atlassian.com/browse/JRASERVER-67177

Please vote for this, I think its critically for all JIRA Admins/Users - that issues does not show up in a filter as expected.

[francis]

This is an old one - I raised one similar back in 2010
https://jira.atlassian.com/browse/JRASERVER-20788

Atlassian decided to not fix it because users would probably depend on the current behaviour ...

Following issue is equally interesting
https://jira.atlassian.com/browse/JRASERVER-23030

That one collects quite a bit of related issues, and you might link to it and also vote.

Francis

[Normann P_ Nielsen _Netic_]

Thanks for the links, Francis !

[Normann P_ Nielsen _Netic_]

Well Atlassian closed the Issue with:

"Hello all,

This kind of behaviour is present for multiple JQL cases e.g. custom fields, labels, projects and is an expected, designed behaviour hence this issue will not be considered a bug.

Cheers,

Pawel, Jira Developer"

, and though I am disappointed, I have learnt now that:

PROJECT = CUSTOMER1 

will return all issues, where as 

PROJECT = CUSTOMER1 AND Classification not in ("Patch Management")

needs to be written as

AND Classification  AND (Classification not in ("Patch Management") OR classification is empty)

to actually show all issues where "Patch Management" is not a value for the Classification Field . So It seems for every negation on fields and labels etc, EMPTY need to be taken in account.