Can I create two db-sourced fields of differing types that use the same data source?

[Rob Horan]

Hi, I would like to know if what I want to do will be possible.

Assume a single data source (database) for a 3 level cascading select field.

The first column would contain parent values (A, B, C, etc), the second would contain child values (A1, A2, A3, B1, B2, etc) and the third would be grandchild values. (A1a, B2b, etc)

Could I then:
1 - In a standard issue, have a multi-value select field that contains ONLY parent level items (A, B, C, etc) for parent tickets
2 - have a cascading selwect field in a sub-task that pulls from the same data source but for all levels, not just the first column dql
3 - craft an automation rule (using automation for Jira) that creates a new subtasks for every distinct value in the parent ticket, see step 1.  The automation rule would  need to set the parent value in the cascading field in the subtasks.

[Veera]

@Rob Horan 

I provided a similar solution for one of our Premium Cloud customers by using External Data for Jira Fields add-on. It'll let you connect to database, weblink or upload a JSON/XML file as the data source. You can even create a field configuration to update specific custom field by comparing other field values including cascading select lists.

If you are using Jira server, Power Database Fields seems to have similar functionality.