Using Cascading Fields with Forms and Assets

[#1]

This workaround is meant to help users that want to use cascading fields with forms or use a 3+ level cascading custom field type.

So this is an option of the workaround from the features below:

•   JSDCLOUD-10792
•   JRACLOUD-7936 

And is meant to help projects where it is necessary to use multiple select options in a field, I used Jira Forms with Assets. In addition, I used as an example a form with the "Country" field in which, depending on the selected country, will open options related to "State" and "City" (all following the selection of each one). This method can be used for other purposes (eg. general and administrative costs).

Important related documentation:

Create or edit a form

Set up the Assets objects custom field

Workaround steps:

• Crete Assets objects schemas

  • Create object schemas for each item that will be used, as well as for each option that will be used on the cascading logic, for my example I used: Countries, States and Cities.

  • It will need to link an object 'Country' to an object 'State' and to an object 'City' as an attribute:
  • Country:
  • 
  • State:
  • 
  • City
  • 

 Remember to mark the option "Allow others to select objects from this schema". For more details about object schemas, please refer to Create an object schema

• Create Assets objects custom fields

  • Create a custom field (assets) for each option that will be used in the cascading values, I created the field "Country", "State" and "City".

  • It will need to use the Filter issue scope (AQL) to reference the object custom field in the order of your cascading logic. In this example: Country > State > City
    
    Using the AQL:

    object HAVING inboundReferences(Name = ${customfield_XXXX.label})

  • Country field:
    
    
  • State field:
  • City field:

 Remember to mark the option "Display a default object when this field appears in a customer portal" to the refered field objects. For more details about object schemas, please refer to What is the Assets objects field?

• Form Settings:

  • Create a form and add an Assets/object field and linked then to the Jira Assets object field:

This workaround will work as shown in the screen recording below:

[Bruna Silva]

Extremely useful! :D

[Charles Trilha]

Nice Article! ProForma Legend, Bruno!

[Wagner Filho]

Amazing article, Bruno! 

[Tomislav Tobijas]

I've recently tested this at one of our client's environments and it worked pretty well. The only thing that didn't work is clearing out the second or third-level field when the first-level field is cleared or when the value is changed → we didn't configure the field so that the default value is displayed.

In general, it's a cool workaround, but it's only relevant if you have JSM Premium or Enterprise plan (so when you have an Assets feature available).

Anyway, really cool and useful article there 🙂

[Bruno Altenhofen]

Hey @Tomislav Tobijas 

Thank you for your feedback! 🙂

Yes, unfortunately, it will always preselect a value that was linked to the Asset object custom field, but you can change it if you have other options, as I show in the screen recording.

Cheers,

[Prathiksha]

This one is super helpful! :D

[Apurbo Mandal]

Perfect learned a lot.

[chaitanaya d]

Hi sir could make it more details on Cascading fields

with below Example: 2 cascading fields

                                   Profession(parent value)

Private Sector(child value)                  Government Sector(child value)

1. Software engineer                            1.police officer
2. Mechanic                                          2.Govenment Officer
3. Doctor