Searches using "is EMPTY" and "is not EMPTY" not consistent

[Christian Soenke]

I try running three different searches:

1) project = MYPROJ AND component in (" COMP1 ", "COMP2") AND status = Open

2) project = MYPROJ AND component in (" COMP1 ", "COMP2") AND status = Open AND "Requirement Id" is not EMPTY

3) project = MYPROJ AND component in (" COMP1 ", "COMP2") AND status = Open AND "Requirement Id" is EMPTY

The results:

1) 95 results

2) 29 results

3) 14 results

I would have expected the sum of 2) and 3) to be 95, but it isn't. It looks like the results of 3) are not complete.

[Nic Brough -Adaptavist- · Accepted solution]

Have a look at the "context" for the field "requirement ID".  I suspect you will find it says something like "Project: MYPROJ and Issue Type: Story".

To take your three queries and explain them, and where I think the other 52 issues have gone on line 4:

1. All issues in my project with status open and one of two components (95)
2. As 1, and with Requirement ID filled in (29)
3. As 1, and with Requirement ID blank (14)
4. As 1, and where the Requirement ID is not a valid field for the issue (52)

What I'm getting at is that "field does not exist" is not the same as "field is empty"

[Christian Soenke]

OK thanks. Your hint helped me to make a filter which takes into account the isue type.