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; } } }

Multiple issue fields conditions with multiple email notifications in one automation?

Matt Crist

Here's my scenario:

I am working with multiple sites. Site name is a field I can use for creating rules.

So, IF Site Name = X, THEN I want emails to go to a certain group.

IF Site Name = Y, THEN I want those emails to go to a completely different group.

I have tried to set up a single automation as follows:

Rule

Result

Rule

Result

Rule Result

So...

IF Site name = X

THEN, Send email to 'List A'

IF Site name = Y

THEN, Send email to 'List B'

IF Site name = Z

THEN, Send email to 'List C'

Unfortunately, my automation didn't work. Is what I'm trying to do possible, and if so, any advice on what could be the problem?

Thanks!

Accepted answers

John Funk

Hey Matt,

You probably need to create a series of IF/ELSE logics with the email created each time with different email list.

You can't copy the send email object in automation, but you can copy and past the email test which should make that go quicker.

All comments

John Funk

Hey Matt,

You probably need to create a series of IF/ELSE logics with the email created each time with different email list.

You can't copy the send email object in automation, but you can copy and past the email test which should make that go quicker.

Bill Sheboy

Hi @Matt Crist

Yes, and...to what John suggests:

I wonder if your email message is identical for the different sites, with only the List A, B, etc. different for the recipients. If so, you could use the IF/ELSE described by John to set a created variable to the recipients, and then use one action to send the email.

To go one step further...if your sites and lists are stable, you could use entity properties to key/value to the site name/list, and then this would be a lookup to get the recipients. Of note: you would want to investigate a better entity property handler than what is available with out-of-the-box Jira.

Kind regards,
Bill

Matt Crist

Yes, the email is exactly the same each time. In the subject line, I am using the following dynamic value: {{issue.fields.summary}}.

The sites and list are fairly stable, but they could change if a new site is added (infrequent) or an employee needs added/removed (more common, but not necessarily frequent).

Thanks to you both for the suggestions!

Matt Crist

I'm not seeing If/Else in here. Is that something I have to configure for it to show up here? Or am I looking in the wrong place?

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud

automation