Details:
Hi Atlassian Community,
I'm facing an issue while configuring cascading asset fields in Jira Service Management (Cloud Premium). My goal is to have two dropdown fields, "University" and "Degree," where the available degrees are filtered based on the selected university.
I created two object types in Assets:
I set up custom fields in Jira for both University (customfield_10203) and Degree (customfield_10204) and linked them to the respective object types in Assets.
The AQL for University is simple:objectType = "University"
This works correctly and shows the list of universities.
- objectType = "Degree" AND "University" = $customfield_10203
- objectType = "Degree" AND "University" = customfield_10203
- objectType = "Degree" AND "University" = University
- objectType = "Degree" AND "University" = "{customfield_10203}"
- objectType = "Degree" AND "University" in $customfield_10203
- "University" = $customfield_10203
When I select a university, the degrees do not filter based on the chosen university. However, if I use objectType = "Degree"
, I get all the degrees listed without filtering, so I know the degrees are there.
Any guidance or insights would be greatly appreciated!
Hi everyone!
I wanted to share that I’ve finally resolved the issue with the dependent dropdown for degrees based on the selected university.
The key was in configuring the AQL correctly in the custom fields for "Universities" and "Degrees." Here's what I did:
In the "Degrees" field (the dependent dropdown), under Filter Scope (AQL), I set the following:
objectType = "Titulación"
This ensures that only objects of type "Degree" are displayed in the field.
In Issue Scope of the Filter (AQL), I added this condition:
Universidad = ${customfield_10203}
This filter ensures that only the degrees related to the selected university in the "Universities" field (customfield_10203) are displayed in the "Degrees" dropdown.
With this setup, when I select a university in the first dropdown, only the corresponding degrees appear in the second dropdown.
If anyone is facing a similar issue, I hope this solution helps! Thanks again for all the support.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.