I am trying to create a rule automation to send notification email to the users selected in a custom field in my issue called "Testing". I tried to use {{issue.Testing.emailAddress}} and I followed the answer to this question https://community.atlassian.com/t5/Marketplace-Apps-Integrations/Send-emails-to-a-user-picker-multiple-users-field/qaq-p/649365 However it didn't work too. I am using next gen pro and the type of the field is people. Thank you in advance
on next-gen sending mails has a bug.
The following bug report deals with it. It mentions "approver" field - but the error message is the same as in a test with a field of type "People" I conducted right now.
Could not send email, the 'To' address field is empty. If you have referenced a field it may be empty.
You can find the bug report here:
https://jira.atlassian.com/browse/JRACLOUD-75376
In some other contributions there was the idea to add components "Re-Fetch data" before executing the actual sending of the mail. I tried it - it did not help.
From the looks the Automation rule alongside with sending the mail like described in your use case is only valid for Classic projects.
Regards,
Daniel
We support this configuration in Notification Assistant for Jira.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
HI @Mohamed Tourab when you create an automation rule. ,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Benjamin
I created this rule but it still doesn't work. I also tried different values in the To field, I tried {{issue.Testing.emailAddress}} and {{#issue.Testing}}{{emailAddress}},{{/}} and {{fieldChange}} but nothing worked so far.
any suggestions ?
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Same here. assuming delivero is muti user picker field, I tried
1- {{issue.fields}}
2- {{issue.fields.delivero.emailAddress}}
3- {{issue.delivero}}
4- {{issue.delivero.emailAddress}}
5- {{issue.delivero.value}}
6- {{issue.delivero.displayName}}
7- {{issue.customfield_10752.emailAddress}}
and non of them give an email address for user picker field. number 3 generates the following:
{
"self= XXXX",
"accountId=XXXX",
"avatarUrls=XXXX",
"displayName=XXXX",
"active=true",
"timeZone=Australia/Melbourne",
"accountType=atlassian"
}
As you can see there is no emailAddress field as if like Automation for Jira cannot see this field.
I have tried API and got all the above fields plus emailAddress. In other words, I can see this field (through API) but Automation for Jira cannot.
I tried changing Actor from "Automation for Jira" to myself and also made the email publicly accessible through Jira configuration. None of them worked.
Regards,
Milad
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.