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

This is a query that was working for me for a few years and as of late no longer reports correctly.

project in (LMX2, LED, LPP2, LSCS, HSF, HA, AP, "SET", TIM, MID, PORT, USMVN) AND issuetype in (Bug, Story) AND status in ("Awaiting QA", "In Progress", Open, "Bug Verify", "In Review", "QA In Progress") AND "Acceptance Criteria" is EMPTY

My issue is that the query returns the same number of results now for "Acceptance Criteria" is EMPTY or "Acceptance Criteria" is not EMPTY.

When I look at the data in  field "Acceptance Criteria" it is present so should not be reporting tickets.  Again this used to work up to just a few weeks ago.

2 answers

0 votes
Jack Community Leader May 10, 2021

Hi David, this is certainly quite interesting. I’m starting to wonder if there’s been some Regression released into a recent update. Only reason I say that because I saw someone else posting something about getting unexpected results when they were looking for a custom feel is empty just yesterday. If you’re pretty confident in what you’re saying but might suggest that you reach out to Atlassian support so they could dive into this a bit and see if maybe there is something that has regressed

Thank you, I will submit a ticket there.

Seems their portal is down at this time.  

Hi @David Cote 

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,


Suggest an answer

Log in or Sign up to answer
Site Admin

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