Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

IS EMPTY operator is not working in my JQL Queries

Mitchell Ekins May 7, 2019

Hi All,

 

I am having difficulty with my JQL queries not behaving correctly, specifically with the 'IS EMPTY' operator.

I search for studies where I know there are empty values (in this case 'worklogComments'), but nothing returns.

I then perform a reverse search using the 'IS NOT EMPTY' and am returned results.

However, this result set does not contain all of the issues ( only returns 62 issues).

I verify this by running another query ignoring this field altogether and get 94 issues back for the same period.

So, from what I can tell, there seems to be an issue with the 'IS EMPTY' operator, but I have no idea what could be happening.

 

Has anyone had a similar issue?

 

- Jimmy.

FULL_QUERY.pngIS_EMPTY_Query.pngNOT_EMPTY_Query.png

1 answer

0 votes
Kat Warner
Atlassian Partner
May 7, 2019

Hi @Mitchell Ekins

When I am running JQL queries about worklogs I keep all the terms about worklogs, for example, worklogComment is EMPTY AND worklogDate >= -32d AND worklogAuthor = currentUser().

The results you are getting may be due to the query trying to filter by issue fields and worklog fields.

Mitchell Ekins May 7, 2019

Hi Kat,

 

The odd thing is, I swear that this was working last week when I actually made the filters.

 

Interesting point though, I will give that a try and see how that goes!

 

I will reply with results on how it went.

 

Thanks for the advice!

Mitchell.

Like Kat Warner likes this
Mitchell Ekins May 9, 2019

Hi Kat,

 

I have played around with it and have come to the realization that I think it is a data issue not a function issue.

 

IS EMPTY is working as expected, but there must be something wrong with how my issues are being saved.

 

Not sure what that could be yet. Will have to keep testing.

 

Thanks,

Mitchell.

Suggest an answer

Log in or Sign up to answer