Use cascading fields in automation

[Mihir Ruparelia]

Hello, 

I am trying to get my head around this. I am currently building a Jira board and in here we have multiple departments, each department with various managers and directors. 

I would need to set up an automation rule that emails the manager based on a cascading field. 

Example: Department select is Customer services, Manager name selected in the child field. This needs to then trigger an email to that person.

Any help on this would be greatly appreciated.

[Charlie Rivarez - CIA · Accepted solution]

Basically you just need to add {{issue.customfield_1234}} which is the cascading customfield then just put "contains" and then input the value of the child.

[Ivan Lima]

There are a few options I can think of to implement this, but depending on the number of cascade options, it can be cumbersome to maintain as a cascade select list. What is the trigger for the notification? Ideally, you could design a solution using a user picker type of field to make it easier to send notifications.

[Mihir Ruparelia]

The trigger will be the Department set and department child field set to the managers name. 

This is what I have tried so far but cannot get the rule to apply.

[Ivan Lima]

Okay, so the trigger is the "issue created" event, and then you have your logic around the cascade custom field to send the notification. I assume you already have an action to send the email.

From an implementation perspective, you could have something like:

Value of the parent:

{{issue.fields.Cascade.value}}

Value of the child:

{{issue.fields.Cascade.child.value}}

Try to play around with that; break your automation into smaller chunks to make it easier to troubleshoot and spot where the gaps are.

[Vish Mande]

@Ivan Lima

Is there way we can match on of the condition instead of "all match" in same IF statement?  Like,

if: A match "value1" OR A match "Value2"

Then: send email

Thanks,

Vish

[Sverrir Tynes [Origo]]

Hi, I have the same issue and my automation is working as expected for issues created in Jira but we are using Issue collector and that is not working at all. Any idea?

Thanks 

Sverrir Tynes
Origo, Iceland