Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Creating a smart value in the "From" field of an incoming JSM email

Robert Munoz August 13, 2021

Excited about the JSM automation capabilities! I'd like to auto-reply from JSM when an email is received with a particular email address. I think you would call the "From" address as the Reporter? So, if I'm on the correct path, I believe I need to create a smart value from the Reporter email and insert it into an automation rule "If" statement and set the smart value condition equal to the particular email address I want to auto-reply to? So my question is, what is the smart value coding for the responder email address? {{issue.reporter.emailAddress}} for example?

Best regards,

Robert M

2 answers

2 accepted

1 vote
Answer accepted
Jack Brickey
Community Champion
August 13, 2021

You don't need to use smart values at all here. Rather you would do something like this...

Trigger - issue created

Condition - reporter is xxx

Action - send email to reporter

 

Now to be clear buy default the reporter will receive a notification when they create an issue, unless of course you have this disabled. If it is not disabled and you proceed with your automation then the reporter will get to notifications.

0 votes
Answer accepted
Alex Koxaras -Relational-
Community Champion
August 13, 2021

Hi @Robert Munoz 

You don't have to use his/her email address. Since you already know his/her username, you just create your automation with conditional statement of that username. Does that make sense to you?

Robert Munoz August 13, 2021

I think so. I'm using "When: Issue created" and "Reporter" "equals". Seems I cant just type the email address, I have to add them as a user in order to select them as a Value?Screen Shot 2021-08-13 at 2.35.38 PM.png

Jack Brickey
Community Champion
August 13, 2021

Are they not already a customer? When they create an issue they would be a customer. Did you try typing the username?

Robert Munoz August 13, 2021

As far as the whole automation goes and what I'm trying to accomplish:

Our users' software uses a particular email to send out automated bug reports to our dev/ops group or in this case back to JSM.  This software email is what I want JSM to use as a conditional "customer/responder" and trigger email for a response back to the user email found in the email subject header/issue.summary. I don't know if I'm making any sense, but getting closer to what I think will work. 

Thanks for your help Jack

 

Robert M

Robert Munoz August 13, 2021

 

They are not a customer. It's our auto-reply email. I've created a user with the email.

I think it works, thanks to your help.

 

Robert M

Jack Brickey
Community Champion
August 13, 2021

Ah….ok well that is important info for sure.

so you should still have the auto reply email as a customer so you can condition on that. Then you will need to extract the email from the subject. I would have to play with that to figure it out which I’m happy to do but it is Friday and I am tuning out for now.

Robert Munoz August 13, 2021

I have a response regarding extracting email address from the subject header here:

https://community.atlassian.com/t5/Jira-questions/Email-located-in-Summary-of-ticket/qaq-p/1751586

I'm at the part of forming the rule and have somewhat of a complete rule but think perhaps it can be better formulated. I have two if statements in series and not sure if it's the most reasonable and logical way to perform the operation.  Below are two snapshots piecing together the rule.

I hope to talk with you more about this next week. Have a great weekend!

 

Robert M

Screen Shot 2021-08-13 at 5.50.10 PM.pngScreen Shot 2021-08-13 at 5.50.29 PM.png

Alex Koxaras -Relational-
Community Champion
August 14, 2021

It seems that I missed the whole conversation, since I was sleeping! :)

@Robert Munoz make sure to mark any answered that helped you as accepted, in order to help other users in this community find the right answers.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events