I have a custom field "QA" on tickets. It is a people field, allowing the ticket creator to add multiple JIRA users to the field.
I'm trying to use automation to send emails to all people in the QA field when a specific action occurs. On the automation event, I cannot select the QA field in the "To:" box.
I've tried using smart fields like {{issue.customfield_10344.emailAddress}} to set the email recipients, but it still doesn't work. Any tips?
Hi Tyler,
Unfortunately we don't have support for this field yet (People field in NextGen projects).
This issue is being tracked at:
https://codebarrel.atlassian.net/browse/AUT-1651
Cheers,
Nick Menere [Head of Product Automation]
Any plans to make this happen? For me, it is quite an important feature.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Jiri Komarek -- Welcome to the Atlassian Community!
I was curious about this one and so retested it...Short version: it still doesn't work
Longer version:
Kind regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I can confirm that this workaround works. Roundabout, but effective.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi, I am also facing the same issue. Could anyone share the workaround for this? I need to get Automation - send email to all users listed in custom People field too. Mine is a team-managed project.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Nur Fatin -- Welcome to the Atlassian Community!
For team-managed projects, the People field type still does not provide the email address to automation rules. Here is the open suggestion to add that: https://jira.atlassian.com/browse/AUTO-519
The two possible workarounds are noted above:
Kind regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you @Bill Sheboy
Is this a limitation of team-managed projects?
Out of curiosity, if the project is a company-managed project, the automation - sending email to users listed in custom People field will work?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
As I understand it, People fields are only used by team-managed projects, including software, Jira Product Discovery (JPD), and Jira Work Management (JWM) types. The missing information such as email address is a limitation of the People field type.
That appears to be one of the reasons Atlassian added the ability to share global, company-managed fields for use with team-managed projects.
Company-managed projects should not have this symptom of missing data such as the email address for user-picker fields.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If that is a multiple select, custom user field, you should see it in the drop down list for TO if the field is available for the project. If not...
You should be able to type in the smart value in the TO field, it will appear below the field, and then you may select it to add it to the TO field. So, please try to enter your field, such as {{issue.QA}} or use the relevant custom field ID.
If that does not auto-magically use the email address attribute, you could also try this to explicitly pull out the email addresses into a list:
{{#issue.QA}}{{emailAddress}}{{^last}}; {{/}}{{/}}
Kind regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Bill Sheboy - thanks for the quick response. The "QA" field is a custom field with type: User Picker (multiple users).
When attempting to use the smart value in the TO line, it is not auto-suggesting the field. I've tried using {{issue.QA}} and the actual field ID {{issue.customfield_10344}} but cannot get it to appear.
No success with using {{#issue.QA}}{{emailAddress}}{{^last}}; {{/}}{{/}} either. I ran a test adding this same snippet to the body of the email, and nothing was returned.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hmmm...
Have you tried that same list syntax with your custom field ID? (I substituted a comma for the semicolon to see if that helps.)
{{#issue.customfield_10344}}{{emailAddress}}{{^last}}, {{/}}{{/}}
And if that doesn't work, perhaps try writing one or more of these values to the audit log to see if it is returning what you expect.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.