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

Dr. Samuel Anim-Addo April 29, 2016

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 votes
JamieA
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 2, 2016

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
TAGS
AUG Leaders

Atlassian Community Events