Cascading dropdowns using Insight JSM Cloud

[Twinit]

We have a scenario where we need to create several cascading fields. Every other field options need to be limited by previous field value during request registration on the Customer Portal.

First field (customfield_001): 

Filter scope (IQL): objectType IN ("Category")

Filter issue scope (IQL): None

Works as expected

Second filed (customfield_002):

Filter scope (IQL): objectType in ("Sub Category")

Filter issue scope (IQL): "Service Category" IN (${customfield_001})

Works as expected

Third field (customfield_003):

Filter scope (IQL): objectType IN ("Modules")

Filter issue scope (IQL): object HAVING inboundReferences(Name = ${customfield_002})

Fails - No options

Object type "Sub Category" has an Attribute of Object type "Category" 

Object type "Sub Category" has an Attribute of Object type "Modules" 

Thanks in advance,

I will appreciate your help very much,

Salome

[Tiago Almeida · Accepted solution]

Hi Salome,

I was able to do this recently on a project with 5 fields/levels, with each one feeding the next one based on its value. The way I did it follows your example, with two adjustments.

I used an extra attribute on the placeholder smart value -- .label, which in Insight was attached to the object's name.

And I used a simpler IQL on the scope, which filtered the schemas' objects by the name/label the customer had selected previously. 

1st field was:

Custom Field: 10180

Filter scope (IQL): objectType IN ("Access Type")

Filter issue scope (IQL): None

2st field was:

Custom Field: 10181

Filter scope (IQL): objectType IN ("Service")

Filter issue scope (IQL): "Access Type" = ${customfield_10180.label}

3rd field was:

Custom Field: 10182

Filter scope (IQL): objectType IN ("Service Category")

Filter issue scope (IQL): "Service" = ${customfield_10181.label}

And so on. The objects themselves need to have an attribute with the previous level dependency set: Service Category needs a link to Service object; Service object needs a link to an Access Type object.

After some searching and testing, this was the document that helped me the most: https://support.atlassian.com/jira-service-management-cloud/docs/configure-the-insight-object-field/#Use-the-Filter-Issue-Scope--IQL--field 

Hope both my reply and link help!

[Twinit]

Tiago, You and your answer helped me very much.

I added '.lable' to the configuration described in my question, and everything worked as expected.

Thank you once again!
Kindest regards,
Salome

[David Harkins]

@Tiago Almeida Thank You for you answer :-) also helped me.