Why do the following queries produce different output:
( resolution != Fixed)
( resolution != Fixed or resolution is empty)
the first query does not show unresolved issue - just resolved set with a resolution which is not fixed. This is confusing
( resolution != Fixed) gives back all issues that have a resolution set (which is NOT "Fixed")
( resolution != Fixed
empty)basically returns ALL issues that have a different value for resolution other than "Fixed" including null values (no resolution at all)
It's a logical thing. You're thinking in more fuzzy human terms, but you need to be precise when you are talking to computers.
The resolution field is either empty or something. When you say "resolution != Fixed", you're thinking "where the resolution is not fixed", but that's not what you've said, because when the resolution is empty, it doesn't have a value at all. So you can't say it's "not fixed" because it's not a valid comparison.
It's a bit like picking up a bag of flour and saying "is that a cake or a biscuit?". It's neither (although one day it could be either), but your question is excluding the correct answer of "neither".
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...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs