nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Automation rule custom field markup

Per Carlén

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":

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

What am I doing wrong?

Thanks!

Accepted answers

Ste Wright

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

Asha Goyal_0i7i5i

Hello @Per Carlén

In addition to what @Ste Wright 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

Bill Sheboy

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

All comments

Ste Wright

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

Asha Goyal_0i7i5i

Hello @Per Carlén

Kindly Accept this if it helps.

Thanks

Asha

Bill Sheboy

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.

Kind regards,
Bill

Per Carlén

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}}.

Per Carlén

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}}.

Per Carlén

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

Asha Goyal_0i7i5i

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

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

automation

markup