link 2 different Cascading fields

Question

hi i am trying to create 3 level cascading sheet for the following data in jira cloud

This is sample data  but in actual i have around 99-100 rows

brandmodelpriceapple14 normal1234apple14 pro5678apple14 pro max2565samsungs122345samsungs12 pro6789samsungs12 ultra5545

however i realized that this option is not possible. then i was trying to create 2 cascading  fields where for the 1st one parent is brand and child is model and for the 2nd cascading firld parent is model and child is price.

now i want the  child of 1st cascading field to be updated automatically in the parent of second cascading field

for example: if in 1st cascading field i select parent as apple and child as 14 pro then i want the parent of second cascading field to be updated automatically as 14 pro and child should be updated as 5678

the first cascading field is in the user story and the second cascading field is in the subtask

Note: this is for jira cloud. not for DC.

Thanks in advance

ram esh · Answer

It would still be difficult because i have arould 90-100 such rows. in the above data i only gave 7 rows as example

Y Dang_Candylio · Answer

Hi @ram esh

I think you should try this way: create a cascading custom field with 2 level 'brand' and 'model' and a number field 'Price'. Then associate them to your project.

Then, using automation with sample rule I show in pics below.

When: Issue created

If: "Phone[Select List (cascading)]" = apple AND "Phone[Select List (cascading)]" = "14 normal"

Then: Edit issue field 'Phone's price' = 1234

Else-if: "Phone[Select List (cascading)]" = apple AND "Phone[Select List (cascading)]" = "14 pro"

Then Edit issue field 'Phone's price' = 5678

I hope this helps!

ram esh · Answer

Hi @Y Dang_Candylio

Thank you for the quick reply. while i wish i could use addon. i am currently not allowed to use addon. we are trying to acheive using the tools available by default.

and the first sujjestion will also not work as they need to have 2 different cascading fields they way they already are because those individual values are being used elsewhere in the issues. so if we change it then we have to change a lot of things.

i just wish there was something we could do with automation.