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

Automation - comment and send email to all users listed in custom People field

Nur Fatin

Hello,

I have two custom fields “Business System Owner” and “Technology System Owner” in my Jira Team-Managed project. It is a people field (multiple user).

I'm trying to use automation to comment and send emails to all users in both fields when a specific action occurs. The comment portion works, but the sending email failed. My Jira Site Admin has added the two fields at the global level. But the sending of email action still failed after I chose both “Business System Owner” and “Technology System Owner” in the “To:” field in the send email action. The audit log states two types of error:

Unable to send the email as the recipient's email address wasn't provided
There is no value set for the field:
- customfield_12874, customfield_12876
- Unable to send the email as the recipient's email address wasn't provided

I also discovered that there are two “Business System Owner” and “Technology System Owner” fields in the fields tab of the project settings.

I have tried to use smart values in the “To:” field, but to no avail. I have tried:

{{issue.customfield_11517.emailAddress}}
{{issue.customfield_11517}}
{{issue.customfield_11516.emailAddress}}
{{issue.customfield_11516}}
{{issue.customfield_12874.emailAddress}}
{{issue.customfield_12874}}
{{issue.customfield_12876.emailAddress}}
{{issue.customfield_12876}}

The comment section works in tagging / mentioning the users when I used:
{{#issue.customfield_11517}}[~accountId:{{accountId}}] {{/}}{{#issue.customfield_11516}}[~accountId:{{accountId}}] {{/}}

But it doesn’t work when I used the audit log customfield values:{{#issue.customfield_12874}}[~accountId:{{accountId}}] {{/}}{{#issue.customfield_12876}}[~accountId:{{accountId}}] {{/}}

Attached are the rule set up, the field tab showing duplicate fields and audit logs.

Is there a way to do this? Thanks in advance.

Screenshot 2025-04-22 at 11.01.46 AM.png Screenshot 2025-04-22 at 11.02.07 AM.png Screenshot 2025-04-22 at 11.03.00 AM.png

Accepted answers

All comments

Akash Singh_vujl0e

@Nur Fatin You're were on the right track, since this is a multi-user picker field, directly referencing the email address using {{issue.customfield_11517.emailAddress}} won't work as expected. The field contains an array of user objects, so you'll need to iterate over that array and extract the emailAddress from each user. These email addresses can then be concatenated into a single string, separated by colons. This resulting string should be stored in a variable, which you can reference directly in your Send email action. Here's the smart value you can use to generate the string:

{{#issue.customfield_11517}}
  {{#if(exists(emailAddress))}}
    {{emailAddress}}{{^last}}; {{/}}
  {{/}}
{{/}}

Nur Fatin

Hey @Akash Singh thanks for the solution. Can I check where should I input the create variable portion in my current rule? Would it be after the "And: Add comment to issue"?

Since there are two custom fields, I just create another one for {{#issue.customfield_11516}}?

I have set it up like this, but couldn't select the variable option and input it as {{BusinessSystemOwner}} and {{TechnologySystemOwner}}:

Screenshot 2025-04-22 at 3.46.40 PM.png

This is the audit log I got when I run it:

Screenshot 2025-04-22 at 3.53.12 PM.png

Am I on the right track?

Thanks in advance.

Akash Singh_vujl0e

@Nur Fatin This seems to be correct, can you add a log action and check the value stored in the variable?

Akash Singh_vujl0e

@Nur Fatin

Apologies for the confusion, I initially assumed that colon-separated emails within a smart value would be accepted in the To field of the Send email action. However, it turns out that when using a smart value, the To field expects a single email address.

That said, there's still a way to achieve the desired outcome. You can use Advanced Branching to loop through each user in the field, as demonstrated in the screenshot below.

Within the branch, you can add a condition to check if the user's emailAddress exists. If it does, you can proceed to send the email to that user. You'll also need to create separate branches for each of the two fields you're targeting.

Bill Sheboy

Hi @Nur Fatin

Do you expect both fields to always contain selected values? If so, you may merge them, remove duplicates, and use that in the email address; no branching is required.

For example, if these are global, company-managed multiple-select user fields:

{{issue.customfield_11516.emailAddress.join(",").concat(",").concat(issue.customfield_11517.emailAddress.join(",")).split(",").distinct}}

That works by joining the selected email addresses together with commas, and then concatenating the values for the two fields. Then they are split back apart into a list before using the distinct function to remove duplicates.

If one (or both) fields could be empty, additional conditional logic is required.

Kind regards,
Bill

Nur Fatin

Hey @Bill Sheboy thanks for the suggestion. I have tried the smart value provided in the "To:" field in the email, but it still returned the same audit log of "Unable to send the email as the recipient's email address wasn't provided."

Sometimes, one field could be empty, but usually both fields will have one or more users.

My project is a team-managed project, does that make a difference?

Thank you in advance.

Bill Sheboy

Just to confirm, what are the types of your fields?

A "People" type field in a team-managed project do not provide the email address for users in automation rules. Here is the defect / suggestion to fix that: https://jira.atlassian.com/browse/AUTO-519

And thus one workaround is to add a global / company-managed user field (single or multiple selection) and use that field in the team-managed project.

Have you done that?

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