Sending an email to a non-jira user

Marcus Chuah February 16, 2022

Hi all, I created a custom field to collect non-jira users email address. Will like to have an automation to send them emails regarding their ticket status. 

 

I been getting this error: 

Advanced branching
The provided smart value was unable to be resolved to an object.
Appreciate any help. Thanks all

Screenshot 2022-02-16 at 16.05.14.pngScreenshot 2022-02-16 at 16.23.55.pngScreenshot 2022-02-16 at 16.23.48.png

2 answers

1 accepted

1 vote
Answer accepted
Pramodh M
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
February 16, 2022

Hi @Marcus Chuah 

Welcome to the Community!!

The issue field value is dereferenced as {{issue.Field Name}} to get the value

Make sure the email is present in the field for the rule to succeed

 ID1.png

ID2.png

Let me know if you have any queries

Thanks,
Pramodh

Marcus Chuah February 16, 2022

Hi Pramodh,

 

Thanks for the reply. I got another error, to address field is empty. Screenshots below. 

 

Thank you. 

Screenshot 2022-02-16 at 17.56.29.pngScreenshot 2022-02-16 at 17.56.23.pngScreenshot 2022-02-16 at 17.56.14.pngScreenshot 2022-02-16 at 17.58.46.png

Pramodh M
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
February 16, 2022

Hi @Marcus Chuah 

Have the Condition checked before sending an email to check whether the field is empty

Mykenna Cepek
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 16, 2022

The "Log Action" is really helpful in situations like this.

Before the "Send Email" action, add an "Log Action" which outputs something like the following (for your particular situation) into the Audit Log before the rule tries to send the email:

Email addr = "{{issue.Email Address[Short text]}}"

This will clarify exactly what that Smart Value is, for that issue, for that rule execution. It will show in the Audit Log.

If nothing shows between the double-quotes, then your Smart Value isn't doing what you think it's doing (so read the documentation again, and experiment as needed until you can see the value you want being returned).

In your case, I also question whether "[Short text]" belongs in your Smart Value. Try removing that.

Marcus Chuah February 16, 2022

Hi all,

 

Thanks for the responses. It is working now. Thank you.

Dias
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 22, 2022

Hi Marcus,

 

How did you get it to working? 

 

I mean how were you able to capture the non-jira user's email address? What did you put as the smart value?

 

Thanks

Marcus Chuah February 22, 2022

I create a custom field called Email Address first - single value to take in inputs at ticket level. Afterwords the automation is written this way. 

Thank you.

Screenshot 2022-02-23 at 10.13.14.png

Like Pallavi Bora likes this
Basavaraj Sangote April 3, 2023

 hi @Marcus Chuah which field type did you used for creating custom field?

Navatha A
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 18, 2024

Hi @Marcus Chuah , this has been really helpful. Thank you 

0 votes
Ashish Bajaj December 19, 2023

Hi Team, The above was hugely helpful.

Thanks.

 

I have another query where I would like to have multiple emails in the field and some can be Jira user and rest may be non licensed Jira users.

Using {{issue.fieldname}}, I was able to add one email address and Jira sent the email but when i used two then the automation failed.

Can someone help.

Screenshot 2023-12-20 140849.png

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events