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

Can't generate user's email addresses

unknown

I am trying to create an automation rule for a template I'm creating that automatically send users in a custom field an email.

When an issue is transitioned in my automation rule i select the the "Send Email" component. In the To: box I entered this code to generate the user's email addresses taken from the users in a custom user field called "Stakeholders".

I don't know why this doesn't generate the user's email addresses found within my user field called Stakeholders.

When I type in

{{issue.Stakeholders.displayName}} it works just fine so I know "Stakeholders" is being recognized.

Any ideas?

Accepted answers

unknown

There is an open defect that team-managed project custom fields do not expose/return the email address (I am guessing through the API) to the smart values:

https://codebarrel.atlassian.net/browse/AUT-1830

It's a bug so this is unresolvable currently.

All comments

Jack Brickey

I haven’t used stakeholders before. I went to the documentation for Smart values but I didn’t see stakeholders. I assume you have validated it? I see your last comment seems to indicate it’s valid but my question is does it actually produce results?

unknown

Sorry "Stakeholders" is a custom multi user field I created. It's populated with a set number of users I would like to send emails to but I can't seem to figure out how to generate their email addresses. Other things seem to work just fine like displayName for example.

John Funk

Hi Christian - Welcome to the Atlassian Community!

Why type of field is the Stakeholders custom field?

unknown

It is a multiuser user picker.

John Funk

Not sure this will work, but might be worth a try. So I would think this would send an email to each person in the list.

{{#issue.Stakeholders}} ({{emailAddress}}) {{/}}

What I am not sure about is if there needs to be some type of separator between them.

OR if this functionality will even work in the TO field of an email for a multi-select field.

unknown

I've tried something similar but user isn't the name of the custom field, "Stakeholders" is so doesn't seem to do anything.

unknown

There is an open defect that team-managed project custom fields do not expose/return the email address (I am guessing through the API) to the smart values:

https://codebarrel.atlassian.net/browse/AUT-1830

It's a bug so this is unresolvable currently.

Nathan Cunningham

That ticket shows it was closed on 10/13/2021 as "Won't Do". Was this issue resolved by other means or are we just dead in the water? Because I'm having the same problem. We have an issue type with a custom people chooser field for "Manager". I want to CC the Manager on automation emails if the assignee doesn't get it completed after X number of days. So I need the email address of the Manager in that custom people chooser field.

Bill Sheboy

Hi @Nathan Cunningham

If you are still seeing the issue they probably didn't map the field.

I haven't tried this for team-managed projects: a work-around you can try if you have the accountId of the user in that field is to call the REST API from the rule to get their email address. Here are a couple of documentation links if you want to try that:

Doing this technique will probably add a few seconds (at least) per rule execution.

Kind regards,
Bill

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