Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How do I have Jira send emails to a "Notify" list when an issue is created or updated?

Hi,

I defined a "Notify" field for my Jira issues, which is a list of people who I want to keep informed about the issue. I would like Jira to email this list of people whenever the issue is first filed, and when it is updated. I tried to create a rule, just to send an email when the issue is created, but I got this error:

image.png

Here is the rule I created:

image.png

 

Thanks,

Richard

2 answers

0 votes
Darryl Lee Community Leader Apr 17, 2021

Hrm, that's supposed to be supported (fixed in AUT-206).

However, I see in the error message:

Nested group

It looks like Automation doesn't support emailing nested groups. Can you confirm that's what you're trying to use that's causing this error? I'm guessing it must be a group that is nested in your external directory, because Jira does not supported nested "local" groups: (ID-167)

Can you test with a non-nested group?

Thanks Darryl. Unfortunately I don't know what any of this means.. I'm using Jira for the first time. I don't know what a nested, group is, or what a non-nested group, external directory or local group are.

Darryl Lee Community Leader Apr 19, 2021

Hi - well, the question is, in the Automation that failed, it failed for a new issue because it somehow couldn't send to whatever group was in the Notify field.

So the first step is to find out who is in that group. Is it a set of users? Or another set of groups?

If you look under Users and Groups, you should be able to find that out:

https://support.atlassian.com/jira-cloud-administration/docs/create-and-update-groups/

Ah, OK. The notify list is just a set of individual people. When I tested the rule, I created a new issue with only myself in the Notify field. I'm the Jira project owner.

Darryl Lee Community Leader Apr 19, 2021

What kind of field is the Notify field? User picker? Or Text Field?

It's a "People" field:

image.png

Here's what the issue looks like - you can see the Notify field has the same entry as Assignee (i.e. me). The format of the entry is different than the Assignee and Reporter fields - not sure if this is relevant.

 

image.png

Darryl Lee Community Leader Apr 19, 2021

Ah, so that's a Next-Gen (now known as a team-managed) project and field.

It appears that People fields work differently in those kinds of projects vs global custom fields used in Classic (now known as company-managed) projects.

According to the Smart Values - users documentation, to reference an email address, you should have been able to use this:

{{notify.emailAddress}

But I just tested this, and that value came up blank. And indeed, when I used the Audit log feature, the JSON blob that was returned did not include an email address.

So it doesn't look like this is possible. :-{

When I did this using a global custom field, I got an address.

So this sounds like a bug. And indeed, I found some related questions:

https://community.atlassian.com/t5/Jira-Software-questions/Automatically-Add-Watchers-from-People-Field-in-Next-Gen/qaq-p/1360184

https://community.atlassian.com/t5/Jira-questions/Not-able-to-set-people-field-through-automation-in-next-gen/qaq-p/1611669

And ultimately I found this bug:

Support the People field (AUT-1651) 

In my testing, it seems like when referencing People fields in Automation, you can get displayName and accountId (which show up correctly in the audit log), but for some reason, emailAddress is not available.

For some background on Next-gen (team-managed) vs Classic (company-managed) projects, here's a good article:

https://community.atlassian.com/t5/Next-gen-articles/Classic-and-next-gen-project-templates-in-Jira-Software-Cloud/ba-p/862404

Thanks again Darryl. So do I just need to wait for the bug to get resolved? I don't see a way to add my email to that bug record, so that I get notified on updates. Do you know if there is a way to do that?

Thanks,

Richard

We support emailing custom field recipients in Notification Assistant for Jira Cloud

Suggest an answer

Log in or Sign up to answer
TAGS

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you