The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

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

Smart values are not populated in email

Andy Smy
July 27, 2023

I didn't find the answer to this question, but I did resolve it, so it might be beneficial to share it.

When I use {{issue:key}} and any field in the format {{issue:<<attribute>>}} the email shows a blank space.

When I use {{key}} and any issue field as {{<<attribute>>}} the email shows the field perfectly.

The smart value documentation does not give any clue as to whether to include the context "issue:" or not.

2 answers

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

1 vote
Answer accepted
John Funk
Community Champion
July 27, 2023

Hey Andy,

Just some clarification, it is {{issue.key}} not {{issue:key}}   dot not colon. Those will work fine for system fields, but probably not with custom field names. 

Andy Smy
July 27, 2023

Well, I'll leave it here for other idiots like me :-) Thanks

Like # people like this
John Funk
Community Champion
July 27, 2023

Haha, we all live and learn. :-)

1 vote
Andy Smy
July 27, 2023

Use {{key}} not {{issue:key}} to include issue Key in automation emails, and similar for other issue fields

e.g.

Email with smart values.png

DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events