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

Hello,

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)
becomes
'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'.

 

BR

Samuel

 

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
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Published May 30, 2018 in Marketplace Apps

Three tips for boosting your board's efficiency with Story Maps

Trello is one of the most effective tools for driving your sprints. It's customizable for every Agile team and product owners and Scrum masters (SM) love it. However, Agile teams often struggle with:...

852 views 2 9
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