nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Cascading fields in automation

Raynara Alves Blaque

Hi there! I need some help with cascading fields in automation, I've created the cascading field "Reason", as you can see in the picture:

Captura de tela 2025-07-11 120506.png

And then on the automation rule, I just wanted that when transitioned, this field couldn’t be empty, so I did like this:

Captura de tela 2025-07-11 120745.png

However, it’s not working right, even with the field filled:

Captura de tela 2025-07-11 121342.png

Could anyone help me with this?

Best Regards,

Raynara.

Accepted answers

Marc -Devoteam-

Hi @Raynara Alves Blaque

Is the field on the screen used for edit action?

Hari Krishna

Hii

Cascading select fields in Jira like "Reason" have two levels – a parent and a child. When you use a condition like "Reason is not empty" in automation, Jira might not evaluate it correctly because it's stored as an object, not as a simple value.

Instead of using the default "is not empty" check, use an Advanced Compare Condition in the automation rule.

Set it like this:

{{issue.fields.customfield_XXXXX.parent.value}} != null

If you also want to check if the child value is selected:

{{issue.fields.customfield_XXXXX.child.value}} != null

Replace customfield_XXXXX with your actual field ID. You can find the field ID by going to Jira > Issues > Custom Fields > locate your field and check the ID in the URL or via Inspect.

This method makes sure Jira correctly checks whether both the parent and child values in the cascading field are selected before continuing with the rule.

All comments

Marc -Devoteam-

Hi @Raynara Alves Blaque

Is the field on the screen used for edit action?

Raynara Alves Blaque

Hi @Marc -Devoteam- I'm not sure I undestand your question right, but I think it isn't. The automation is just to certify that someone didn't forget to fill the field, and if he/she did it, the card is changing columns and a comment will be made to inform.

Marc -Devoteam-

Hi @Raynara Alves Blaque

The message in the audit log says it can't find the field.

See KB, resolve-automation-rule-failure-due-to-missing-configured-field-in-jsm-cloud

Hari Krishna

Hii

Instead of using the default "is not empty" check, use an Advanced Compare Condition in the automation rule.

Set it like this:

{{issue.fields.customfield_XXXXX.parent.value}} != null

If you also want to check if the child value is selected:

{{issue.fields.customfield_XXXXX.child.value}} != null

Replace customfield_XXXXX with your actual field ID. You can find the field ID by going to Jira > Issues > Custom Fields > locate your field and check the ID in the URL or via Inspect.

This method makes sure Jira correctly checks whether both the parent and child values in the cascading field are selected before continuing with the rule.

Raynara Alves Blaque

Hii Hari! Thank you so much for your anwser, it worked here! The only thing I did was to look up for the field propor custom name in the smart values { } -> custom fields.

I belive the issue of not finding it before was because there's in another board one field with the same name.

Thank you both @Hari Krishna and @Marc -Devoteam- !

Captura de tela 2025-07-11 134114.png

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud