When a user was searching with the following filter, issues with no component values set did not appear in the search results. Any idea why?
project = XYZ AND component != "ABCDEF" AND status != Closed ORDER BY key DESC
where ABCDEF is a component in project XYZ.
By "no component values set", I mean the Component was blank or None.
Perfect. I shortened it to the following:
project = ABC AND (component != "ABCDEF" or Component is empty) and status != Closed ORDER BY Key DESC
and this seems to work as well.
But I still don't understand entirely why we have to add the "Component is empty" part. Something to do with databases and nulls versus empty strings in a query?
It's not just because the database works that way, it's because the world works that way and a database reflects it.
Think of the question "what colour is your cat?". Possible answers might be tortoiseshell, ginger, black, and grey, so you can ask select questions like "show me all the cats that are not ginger". But "I don't have a cat" is also an answer, and one that should clearly not show up in a select question.
In logical terms, "null" is something different from "yes" or "no" and needs to be handled clearly and distinctly.
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!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot