Forums

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

AND NOT "" is EMPTY is being appended to filters

loan_nguyen
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
June 18, 2025

We recently updated our Jira version to 10.5.1 and we are noticing that AND NOT "" is EMPTY or AND NOT "Issue Type" is EMPTY is being appended to JQL filters when clicking from Dashboard Total Issues on PIE charts causing an error to the JQL filter itself returning zero results. 

 

Is there a fix in place for this?

image.pngimage.png

2 answers

1 accepted

0 votes
Answer accepted
Vitalii Rybka
Contributor
June 18, 2025

Hi loan_nguyen,

This looks like a bug introduced in Jira 10.5.1 with dashboard pie chart interactions.

Immediate workarounds:

  1. Edit the JQL manually - remove the AND NOT "" is EMPTY clause when it appears
  2. Recreate the pie chart gadget - sometimes fixes the malformed query generation
  3. Use Issue Navigator directly instead of clicking through the pie chart

Is there an official fix? This appears to be a regression bug. I'd recommend:

  • Check Atlassian's Known Issues page for 10.5.1
  • Contact Atlassian Support with your specific JQL and reproduction steps
  • Consider downgrading temporarily if this is blocking critical workflows

The empty string condition AND NOT "" is EMPTY is clearly malformed JQL, so this should be on Atlassian's radar for a patch release.

Anyone else seeing this issue in 10.5.1? Would be good to know how widespread it is.

0 votes
Carlos Garcia Navarro
Community Champion
June 18, 2025

Hi @loan_nguyen ,

Welcome to the Community! I don't know why those clauses would be appended to the filters. Regarding the specific error in the screenshot, can you replace "Issue Type" with issuetype?

loan_nguyen
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
June 18, 2025

Hi, the manual workaround is an option.  However, we have a lot of users that will need to do this and some may not be as comfortable to update the JQL to get it to work.  They will simply see an error to the filter when it used to work fine up until now. 

Suggest an answer

Log in or Sign up to answer