Why in JQL not equal value does not return fields that are empty?

One of my users raised this question: 

  • If you do project = A and fixVersion = 1.0 you get X issues.
  • If you do project = A and fixVersion != 1.0 you get Y issues
  • Now X+Y is not the total number of issues in project A

I explained him that he can test for empty values using fixVersion IS EMPTY but he correctly pointed that the real-life scenario is with much more complex filters and this limitation does makes them much more complex.

Any workarounds? Is this a bug or is by design?

2 answers

0 votes
Ollie Guan Community Champion Oct 28, 2014

some issue fixversion is empty

you can try like this query

 (project = A and fixVersion != 1.0) and (project = A and fixVersion is empty) 

0 votes

"does not equal" is not the same as "is empty".  Two points - first, the field may not be valid for an issue, and second, version is multi-select.  So your project could have

Issue 1:  No fix version

Issue 2:  Fix version = 1.0

Issue 3:  Fix version is not a valid field

Issue 4:  Fix version = 1.0 and 1.1

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,903 views 19 22
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