i'm using automation for output in email but in email body below smart value is not working

[Shiwanshu Singh]

The below Smart values is not working in my email body

<td>{{Impact Severity}</td>
<td>{{RFC Priority}}</td>
<td>{{issue.customfield_10064}}</td>

<td>{{issue.customfield_10070}}</td>

[Hans Polder _Devoteam_]

Hi Shiwansu,

Quick shoutout, in the underlined part below, I notice that there is only one }. This should always be two }} like you did with the others.

Can you please adjust this and let us know if your initial part works?

<td>{{Impact Severity}</td>
<td>{{RFC Priority}}</td>
<td>{{issue.customfield_10064}}</td>

<td>{{issue.customfield_10070}}</td>

[Shiwanshu Singh]

I've identified the issue. When the query is executed, the severity field is returning a None value along with actual data. Due to this, the email is showing a blank entry. Is there a possible solution to handle this?


 

[Bill Sheboy]

Hi @Shiwanshu Singh 

Smart values are name, spacing, and case-sensitive...and they often do not exactly match the field name displayed on the work item views.  When an incorrect smart value is used, that returns as null, often failing silently in the rule.

Please find an example work item with your fields and then use this how-to article to identify the correct smart values (or custom field ID) to use:

https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/

And if you do not see the field in the results, it may not be supported by automation rules.  In those cases, one may try directly calling the REST API endpoint rather than the Lookup Work Items action.

Kind regards,
Bill

[Shiwanshu Singh]

This was helpful

Thanks 

[Shiwanshu Singh]

Can you help me with this as well
i have two field business approval and technical approval and i got the value for technical approval but not getting for business approval

[Bill Sheboy]

What are the types of those fields: text, single-select option, multiple-select option, user, etc.?

The field type impacts how they are accessed in rules.  You should be able to see how they are stored from the how-to article I provided.

Perhaps if you post your current complete rule and the Send Email Action details it will provide more context to help. Thanks!

[Shiwanshu Singh]

I want value for highlighted one
Please help 

[Bill Sheboy]

For a single-select option field, please add the value attribute to get what you see in the dropdown list.  For example, if the work item is a single one, that would be:

{{issue.customfield_12345.value}}

Remember to use your smart value (or custom field ID) for the "Business Approval" field.

[Shiwanshu Singh]

I had already tried, but I didn't get any value.

[Bill Sheboy]

Please post the following as they may help explain this symptom:

• an image of your complete rule in one single image for continuity
• an image of the rule action where you are trying to use that smart value expression
• an image of the audit log details showing the rule execution with all the areas a the right side expanded to show the impacted work items

Thanks!

[arielei]

Hey @Shiwanshu Singh 
please share an image of the automation part where you send the email

[Shiwanshu Singh]

invalid

[Shiwanshu Singh]

and when i m adding log didn't get input

[arielei]

Hey @Shiwanshu Singh 

Are the other custom fields appear in the email?
If so, are you sure they are present in the work-item?

[Shiwanshu Singh]

yes rest all appear
And I'm sure the work-item is present

[arielei]

Hey @Shiwanshu Singh 
I suggest that you will write a log before you send the email with all the fields you want to send, and then run in without sending an email so you can play with it and see whats going on.

Furthermore, try to use the name of the field instead of "Custom Field_....".
you can also try using {{issue.field."Name Of Field"}} in all your cases.

Action in Automation is called "Audit Log" - try it and see what you got.

Good Luck

Ariel.

[Shiwanshu Singh]

not getting output for this

[arielei]

Hey @Shiwanshu Singh ,

See my last response, {{issue.fields}} is not enough, you need to specify the field name you want to see.

Like:
{{issue.field."Name Of Field"}}