Cascading fields: automation question

FrancoB

Hi everyone,

I would like to ask for your advice.

Currently, I use a plugin to manage 6 cascading fields. Unfortunately, I recently discovered that this plugin does not allow selecting values through automation using the value itself, but only by using the ID, which is not suitable for my needs.

I do not have much experience with Assets, but I understood that they might be used to manage related fields. Is that correct?

Also, through automation or API, is it possible to select a field value by passing the value itself (for example “Hardware”), or is it always necessary to use the ID?

Thanks

C.Faysal {CFcon}

Great question! To address both points:

Assets for cascading/related fields Yes, Assets can model hierarchical relationships and are queryable via automation using AQL. But it's a significant architectural shift: you move from simple select fields to object references, which adds complexity around schema design and permissions. Worth it for very complex setups, but probably overkill if you just need cascading selects.

Selecting values by name instead of ID With native Jira automation and the REST API, you can absolutely reference select field values by name, not just ID. The API accepts {"value": "Hardware"} for standard select fields, and Jira Automation supports name-based matching as well.

The ID-only limitation you're hitting sounds like a constraint of your specific plugin's implementation, not a general Jira restriction. If it wraps field logic in its own layer, it may force you through its internal ID scheme.

A couple of questions that might help narrow this down:

• Which plugin are you using?
• Are you updating the field via native Jira Automation, API, or a third-party tool?

Depending on your setup, native Jira cascading select fields (without the plugin) might already solve your problem.