Unexpected Results with JQL and "Request Type"

I am getting what appear to be inconsistent results with a JQL Query. In my database, I have 4153 tickets. I noticed some pecularities when running queries with "Request Type" and whittled it down to the following scenarios:

"(("Request Type" is empty) or ("Request Type" is not empty))" yields 4001 tickets (4153 were expected)

"not (("Request Type" is empty) or ("Request Type" is not empty))" yields 0 tickets (0 were expected)

Any ideas?

I am using JIRA v6.3-OD-08-005-WN

1 answer

1 accepted

0 votes
Accepted answer

What type of custom field is "Request Type"?

Also, could you check the field context and the field configurations - I suspect you might find 152 issues are in projects that the field does not exist for.

Ran into it on Friday myself. I know it sort of makes sense when you think it through, but it's not obvious or intuitive! And I keep forgetting it.

That was some amazing psychic debugging you just performed - you were exactly right.

When I restrict the query to a specific project, things work as expected.

Thanks for the quick reply!

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

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

2,711 views 17 21
Read article

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