nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Filtering on resolution

Martin Buchleit1

Why do the following queries produce different output:

( resolution != Fixed)

and

( 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

Accepted answers

Christian Czaia [Decadis AG]

( resolution != Fixed) gives back all issues that have a resolution set (which is NOT "Fixed")

( resolution != Fixed or resolution is empty) basically returns ALL issues that have a different value for resolution other than "Fixed" including null values (no resolution at all)

All comments

Timothy

Because "Fixed" is a resolution and there are many other resolutions.

Nic Brough -Adaptavist-

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".

Christian Czaia [Decadis AG]

( resolution != Fixed) gives back all issues that have a resolution set (which is NOT "Fixed")

( resolution != Fixed or resolution is empty) basically returns ALL issues that have a different value for resolution other than "Fixed" including null values (no resolution at all)