Why does a stored filter change NULL to EMPTY on Scripted Field?


Filters (saved queries) on our JIRA 6.2.2 instance cannot persist a query for NULL values in a custom scripted field.
The unsaved query does not change in the Issue navigator.

For example:
'Release Date' is NULL (or, customfield_12001 is NULL)
'Release Date' is EMPTY

However, when the query is stored as a filter, the '"custom scripted field" = NULL' changes to '"custom scripted field" = EMPTY'.

The searcher in use is 'Natural Searchers for JIRA'.





1 answer

0 vote

I'm not quite sure I understand, but, does it matter? Do you get different results? "is empty" seems more correct to me than "is null".

Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Bridget Sauer
Published Thursday in Marketplace Apps

Calling all developers––You're invited to Atlas Camp 2018

 Atlas Camp   is our developer event which will take place in Barcelona, Spain  from the 6th -7th of   September . This is a great opportunity to meet other developers and get n...

74 views 0 5
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