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:
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:
Set up the Assets objects custom field
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.
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 a custom field (assets) for each option that will be used in the cascading values, I created the field "Country", "State" and "City".
object HAVING inboundReferences(Name = ${customfield_XXXX.label})
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?
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:
Bruno Altenhofen
Atlassian Engineer - The guy from Proforma(Jira Forms)
e-Core
Krakow - Poland
1 accepted answer
12 comments