Why are empty fields omitted from != queries?

I have a field called "fixVersion" I use to track when an issue was fixed or when it is scheduled to be fixed.  If I do a search for fixVersion != "6.0", the results show items where fixVersion is not assigned to "6.0", but omits items where fixVersion is empty.  Why does this query 'fixVersion != "6.0"' give me fewer results than this query 'fixVersion != "6.0" OR fixVersion is EMPTY'?  Shouldn't EMPTY also be not "6.0"?

1 answer

In database terms, there is a difference between a field with a value and a field with no value(never set).   You can read why by looking up why SQL has an "IS NULL" condition.   You can see this effect on SQL when you try to do joins as well (ie. the difference between inner join and any one of the forms of outer joins)

Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Julia Dillon
Posted Tuesday in Jira

Tell us how your team runs on Jira!

Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...

202 views 1 18
Join discussion

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