Automation rule custom field markup

Per Carlén March 15, 2024

I'm setting up an automation rule that creates a message in Microsoft Teams and I want to include some custom field data (of the issue) in the message but it does not get included in the messages. For example, I'm using this markup for the custom field "Customer":

{{issue.[Customer]}}

I can't even get native fields like "Summary" to show up with that markup:

{{issue.summary}}

What am I doing wrong?

Thanks!

3 answers

3 accepted

2 votes
Answer accepted
Bill Sheboy
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.
March 16, 2024

Hi @Per Carlén 

Context is important for automation rules.  The symptoms you note could be caused by where the smart values are accessed within the rule.

For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected.  Those will provide context for the community to offer ideas.  Thanks!

Kind regards,
Bill

Per Carlén March 18, 2024

Thanks! I will do that in the futer.

The problems in this case was that I didn’t use the proper syntax. I included the brackets around the custom fields and I didn’t use the correct casing for{{issue.Summary}}.

Like AG likes this
AG
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.
March 18, 2024

Thanks @Per Carlén Appreciate the way you responded and hope it should help others.

1 vote
Answer accepted
AG
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.
March 16, 2024

Hello @Per Carlén 

In addition to what @Stephen Wright _Elabor8_ suggested, I would kindly like you to check and confirm if there are custom fields with the same name. Also, if that is the case or not, to avoid any confusion, you could try using custom field id to display the correct value  {{issue.customfield_XXXX}} or {{issue.fields.customfield_XXXX}}

Kindly Accept this if it helps.

Thanks

Asha

Per Carlén March 18, 2024

Thanks! Your answer made me realize that I had included the brackets around the custom fields. Removing them solved the part of the problem.

Like AG likes this
1 vote
Answer accepted
Stephen Wright _Elabor8_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 15, 2024

Hi @Per Carlén 

Does this work on internal Automation Rules (i.e without Microsoft Teams involved)?

Also - ensure you're using the actual field name - smart values are case sensitive - eg. it might be {{issue.Summary}}, or {{issue.Customer}}.

Ste

 

Per Carlén March 18, 2024

Thanks for your help!

My mistakes was that I included the brackets around the custom fields and didn’t use the correct casing for {{issue.Summary}}.

Like # people like this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events