Jira Search not returning results for empty cascading list

[mon33h]

I have several Jira tickets that have empty values for both options of a custom cascading list.

I am trying to search for these tickets (excluding those that do have a value in the cascading list), however the search is not returning all of the tickets that meet this criteria.

For example:

The following two tickets have no values selected for the custom cascading list called ‘Application Area’

When I apply the filter to only show those with no options selected for ‘Application Area’, only one of these tickets is returned, when I would expect both to be returned. See below all of my different search attempts, including those as suggested on this page: https://confluence.atlassian.com/jiracoreserver0817/advanced-searching-functions-reference-1071817188.html#Advancedsearchingfunctionsreference-cascadeOptioncascadeOption()

If I do the opposite search, i.e. where values have been selected for ‘Application Area’, the search works as expected and neither of these tickets are returned. For example:

If anyone could provide advice/guidance on how I can get this search to work that would be great.

Thank you

[Ste Wright · Accepted solution]

Hi @mon33h 

I recreated this in one of our environments, and it works fine for me using...

project = ABC and "Cascading Field" is EMPTY

This was tested across Issues with no values, with one value, and with both populated.

I'd suggest reindexing Jira as a first step, and see if that resolves the issue - see: https://confluence.atlassian.com/adminjiraserver/search-indexing-938847710.html

Ste

[mon33h]

Hi @Ste Wright ,

Thank you for your suggestion - we performed a re-index overnight and the search appears to be working as expected today.

Appreciate your help.

Cheers

[Elliot Canfield]

I was just searching this looking for a solution, and also found the struggle. The workaround I finally came up with (surprised Atlassian did not comment on this) uses only the basic JQL functions, no plug in or scripting needed.

Simply put - use the "Not IN" operator and filter out ALL possible child values

Pre-Condition:
Parent Value cannot contain the same value as any Child value, and parent value is populated

JQL function:

1. YourCascadingField not in ("child value1",""child value2","child value3",...etc.)
2. YourCascadingField in ("parent value1", "Parent Value2") and yourCascadingField not in ("child value1",""child value2","child value3",...etc.)

To get results if the field is completely empty, try this:

• YourCascadingField is EMPTY

[Pramodh M]

How about only this search?

location in cascadeOption(none)

Remove the key part, you should be able to get the list of issues if both the fields are not present

Let me know the result @mon33h 

Thanks,

Pramodh

[mon33h]

Hi @Pramodh M ,

Thanks for your reply.

The reason why I have filtered by those two keys, is to demonstrate that the search is not returning all results with no options selected for the cascading list.

On the greater scale (when I do not include those keys in the search for the demonstration), 40 tickets are returned, when I know that there are actually 381 tickets that do not have any values selected for this cascading field. So the search is not applying the filter correctly, as it is missing 341 tickets that also have this cascading field empty.

That is what I am trying to explain in the demonstration above - there are two tickets, both do not have any options selected for that cascading list and then when I apply the filter to display only the tickets with no options selected for that cascading list, only one of those tickets is returned (when both should be).

I hope this helps to clarify?

Thanks

[Steve Letch]

Having the same issue as you @mon33h it just messed up my automation rules because I wanted my rule to run when one of my cascading select fields is empty