Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

JQL Filter for "custom field is EMPTY" returns results where Custom field is "not" Empty

I wrote a JQL query to find the issues which are not proper filled with data. In this query I ask for a custom field which shows the planned start date of an issue. This field is a Date Picker Field.

customfield is EMPTY

But as a result I get differt issues where this custum field ist filled.

Even if I use

customfield is EMPTY and customfield is not EMPTY

I get results.

I already read that I should do a Re-indexing. But in the newer versions of Jira Cloud that seems to be no longer possible.


Thank you in advance for your Help.

1 answer

1 accepted

1 vote
Answer accepted
Jack Community Leader May 10, 2021

I have never experienced this before. Could you share a couple of examples of the results you get returned where the field is not empty. By the way, indexing happens automatically in the background in cloud so you don’t have to worry about that. 

Hi @Dennis Lex  -- Welcome to the Atlassian Community!

As Jack noted, indexing is automagic for cloud, and...

Do you have any team-managed projects (next-gen) in use in your instance?  If so, I suspect this may be related to the problem with JQL and EMPTY tests confusing fields between projects, as noted here:

The work-around is to use the custom field ID in the query.  You may learn how to find the ID from that defect posting.

Best regards,


Like Dennis Lex likes this

Thank you for your warm welcome to the Atlassian Community and your competent answers. @Jack @Bill Sheboy 

Bills work-around worked for me and I guess as he mentioned that it belongs to the next-gen version of Jira Cloud that we recently introduced.

I wish you a nice week.

Best regards,


Like Bill Sheboy likes this

Suggest an answer

Log in or Sign up to answer

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you