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

"To" field for triggering an E-mail Notification is not taking the "Assignee" value of an issue.

Hi all, 

Im working on  an automation rule for triggering an email notification depending on some filter criteria for some issues.

there is an error in the audit log.

Could not send email, the 'To' address field is empty. If you have referenced a field it may be empty.

Can someone tell me why this is happening.

3 answers

Hi @rish_kr221 , welcome to the community!

In order for the email to be sent successfully, it needs to have a recipient. If you have, for example, configured your rule to send an email to the task's assignee at a certain point in a workflow, if the task does not have an assignee when the rule is triggered, the rule will fail as it has no one to send the email to.

In your automation rule, which field is being used in your To: field in the email action?

0 votes
Curt Holley Community Leader Jun 02, 2021

Based on the error message, it is either as @Callum Carlile _Automation Consultants_  has described, or you haven't opoulated the "To" field of the Send email Action.

mail0.png

0 votes
Daniel Ebers Community Leader Jun 06, 2021

Hi @rish_kr221

for using the Assignee it should just work according to the hints from Curt and Callum.

In case you would be using a "team-managed project" alongside with a people field it might be you are running into this effect: https://jira.atlassian.com/browse/JSWCLOUD-20774
I don't assume this matches with your case but in case you could confirm Community members might be able to advise further.

Regards,
Daniel

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

322 views 9 7
Read article

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