Insight custom field with issue scope IQL based on cascading select custom field

[Stefan Bogdan Cimpeanu]

Hello,
We have a cascaded select custom field.
We also have an Insight object field.
We want to set issue scope (IQL) for the insight object using placeholders for the first selection in the cascaded select field, but can't find the correct way.

We tried objectType =${customfield_10207.${1}} , objectType =${customfield_10207.${0}}, and other variations, but can't get the correct value.

For a particular issue, the value for the cascaded filed looks like this: [null:Domain name services, 1:Change domain] , where 'Domain name services' is the first select option, and 'Change domain' is the second option.

For regular select fields, the insight issue scope IQL works just fine as: objectType =${customfield_10204.name}

Please advise how to create the IQL correctly.

[Björn Gullander]

Hi

Cascading list values are a hazzle. And I'm not sure Cascading fields are supported by placeholders and I don't get anything to work like your example. (https://documentation.mindville.com/display/INSSERV/Placeholders+in+post+functions)

However, the syntax for multi-valued placeholders should be like this (with no dot): 

first item: ${customfield_10207${1}}

second item: ${customfield_10207${2}}

all items: ${customfield_10207${0}}

Would it not be possible to replace the cascading field with two Insight fields instead (one parent and one child field ) and that the child field value is referred by the field you are trying to filter?

Björn