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.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Well, I'll leave it here for other idiots like me :-) Thanks
Haha, we all live and learn. :-)
Use {{key}} not {{issue:key}} to include issue Key in automation emails, and similar for other issue fields
e.g.
Still have a question?
Get fast answers from people who know.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.