How to display custom field for #LookupIssues using smart value?

[Rich]

I have set up automation to send a notification after looking up issues. I'm able to include all built-in issue fields in the email but I'm having difficulty including custom fields.

I looked up the smart value for a custom "Date of Last Status Change" field 

"customfield_11180": "Date of Last Status Change",

and then I tried to include the smart value in the email text but it won't display. It looks like the value that Jira returns via the API call is 

"customfield_11180": "2020-10-16",

My email text is below:

Below are the current tasks that haven't changed status > 1 week:
<br><br>
<table>
<tr style="border: 1px solid black">
<th style="text-align: left">Assignee</th>
<th style="text-align: left">Summary</th>
<th style="text-align: left">Status</th>
<th style="text-align: right">Last Updated</th>
<th style="text-align: right">Custom field</th>
</tr>
{{#lookupIssues}}
<tr>
<td>{{assignee.displayName}}</td><td><a href={{url}}>{{summary}}</a></td><td>{{status.name}}</td><td style="text-align: right">{{updated.shortdate}}</td><td>{{customfield_11180}}</td>
</tr>
{{/}}
</table>

Any ideas?

Thanks in advance.

Rich

[Esther Strom · Accepted solution]

Welcome to the Community, @Rich

I'm afraid this isn't going to be what you want to hear, but at this time you can't use custom fields with #lookupIssues.

Here's the documentation.

A suggestion ticket for this use case was opened in Atlassian's Jira earlier this month. Vote for it, watch it, and hopefully it will be implemented.

[Krister Broman _Advania_]

For Reference to others that are looking for this information

Adding custom fields to Lookupissues does now work for cloud, communicated here: 

https://community.atlassian.com/t5/Automation-articles/New-lookup-issues-fields/ba-p/1873978

[baoduy]

If we only need to access custom field via a specific item in lookupIssues list, it could able to achieve this by following these steps:

- Use Branch rule / related issues -> Type of related issues: JQL, with search input: key = {{lookupIssues.get(0).key}}

- Access the custom field normally via smart values inside the Branch rule / related issues: {{issue.customfield_10091}} (on my case is multi select custom field))