Custom multi-level cascadedrop values not appearing in filter dropdown when searching

[Andy Leitzinger]

I created a 2 level multi-level cascadedrop custom field and assigned it to bugs, stories, tasks, epic, sub-task and a custom Issue type I created in my Jira project.  There are 4 root level values and around 20 2nd level values.

When I create a new bug, task etc. the values appear in the drop down to select from but when I try to search using "Filters" and and choose the field the only value that appears in the dropdown is "Any".

If I "Switch to JQL" on my filters I can search and successfully retrieve search results.

Note: I assigned this user defined field to a custom issue type I created and when I filter on this issue type the drop down values do appear, unlike when I select bugs, stories, tasks, epic, sub-task

[Nic Brough -Adaptavist-]

If you are using the app I suspect you are to provide the mult-level cascading select field, then yes, you are stuck, that's the way it has been coded to work in the search, and there's nothing you can do to change it.

You'll want to get in touch with the authors of the app to see if they have plans to improve the way the field works in search.

[Andy Leitzinger]

I am not using any Jira extensions, only the core cloud Jira project.  Why would the drop down in the search (Filters) display the values for one Issue type and not others when I have associated the same user defined field with all of the Issue types?

[Nic Brough -Adaptavist-]

Jira Cloud does not have a multi-level cascading select list field type.  You can only get one by adding an app.

[Andy Leitzinger]

Hi, My mistake, you are correct. There is a "JIRA Toolkit Plugin" installed.  This must be providing this field. This is an Atlassian extension.

[Nic Brough -Adaptavist-]

Nope, the Jira Toolkit does not provide a multi-level cascading select field.

But I think we may be drifting away from the problem.

The message you're seeing in the screenshot (thanks for adding that, it wasn't there when I first answered) makes me want to check exactly what the context settings are - does the field have more than one context?  If not, is the context set to global?

[Andy Leitzinger]

Just to clarify that I use the multi-level cascading field on the same form used by multiple Issue types including a custom issue type I created.

When I create a new record of any of the issue types the multi-level cascading field displays properly on the form for all of the issue types.

When I try searching using "Filters" when I select my custom issue type and then try filtering by the multi-level cascading field is works fine.

It's only when I select the other issue types (bugs, story, task, epic) and then try filtering by the multi-level cascading field does not work and shows "Any" as the only option.

[Nic Brough -Adaptavist-]

Ok, but does the field have more than one context?  If not, is the context set to global?

[Andy Leitzinger]

It is available in 1 context. Doesn't say 'global context' anywhere I can see. 

[Nic Brough -Adaptavist-]

Bother, the UI changed since I last looked (well, paid any attention!). 

Can you click on the  "1 context" and tell us the text of the resulting pop-up box?

[Andy Leitzinger]

 "This custom field has the following 1 context applied.Create, edit or delete contexts

Default Configuration Scheme for AreaDefault configuration scheme generated by Jira

This field will be available on issues of types Epic Bug Story Product Roadmap Feature Task in all projects

This field will not appear on any issues that do not match the above contexts. "

[Andy Leitzinger]

Anyone have any suggestions?