Unable to run automation on custom field and smart values using LookupIssues

[tasha tokunova]

I need a rule that will run on schedule, check JQL and send a list of tickets to a user.

I have issues with smart values when "send email"

Here's the email content:

{{#lookupIssues}}
<li>{{issuetype.name}}
Key+Summary: <a href="{{url}}">{{Key}} - {{summary}}</a>
All comments: {{comment}}
Returns last comment: {{issue.comments.last.body}}
Custom field value: {{issue.10033}}
</li>
{{/}}

When an email gets triggered I get blank values I miss {{issue.comments.last.body}} and {{issue.10033}}

[Bill Sheboy · Accepted solution]

Hi @tasha tokunova 

When your rule is inside of the {{lookupIssues}} you no longer use the {{issues...}} prefix to the smart values.  Their context is the lookup, and {{issues...}} refers to other contexts, such as either the trigger issue or issues within a branch.

Please try this: inside of the lookup iterator  {{comments.last.body}}

Kind regards,
Bill

[tasha tokunova]

Oh wow! Thanks, Bill, it works! 

{{comments.last.body}} fixed

Do you know how to fix smart value to return custom filed body?

Custom field value: {{10033}}

This doesn't return the value ^

[tasha tokunova]

I think I was able to find the answer, this is the way to go:

Custom field value {{fields.customfield_10033}}

Thanks @Bill Sheboy again! 

[Bill Sheboy]

I am glad to learn that helped!

By the way, when you are trying to find the correct smart values to use for a field, this how-to article can help.  Basically you find an example issue and call the REST API from a browser tab to list all possible smart values.

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

[maurício heberle]

@tasha tokunova thank you for the custom field syntax. It wasnt described anywhere

[tasha tokunova]