{{issue.Request Type.requestType.name}} does not return value in a list in automation

[Ivan Mizzi]

I've created a scheduled automation that sends out a report. Everything is working as expected except for {{issue.Request Type.requestType.name}}. Excerpt of usage shown below:

{{#lookupIssues}}
<tr>
<td><a href='{{url.customer}}'>{{key}}</a></td>
<td>{{summary}}</td>
<td>{{issueType.name}}</td>

<td>{{issue.Request Type.requestType.name}}</td>
<td>{{priority.name}}</td>
<td>{{status.name}}</td>
<td>{{reporter.displayName}}</td>
<td>{{created.jqlDate}}</td>
<td>{{project.name}}</td>
</tr>
{{/}}

And for the record, yes, Request Type is filled in for all issues returned from that query.

[Bill Sheboy · Accepted solution]

Hi @Ivan Mizzi 

Your rule is using the Lookup Issues action, with an iterator over the values:

{{#lookupIssues}}
   ...
{{/}}

Once inside of the iterator, the prefix of issue, such as with {{issue.some field}} is not needed as the scope is now the iterator (i.e., lookupIssues).  Please try removing the prefix and re-testing.

Kind regards,
Bill

[Ivan Mizzi]

Hi @Bill Sheboy 

I tried all these variations in a desperate attempt:

<td>{{issue.Request Type.requestType.name}} - {{issue.Request Type}} - {{requestType.name}} - {{issue.Request Type}} - {{Request Type.requestType.name}} </td>

The one in bold works, just in case anyone else has the same difficulty.

[Maria I. Ivanova]

@Ivan Mizzi Thank you for updating with the solution that you found! I've been struggling to display the Request Type name in the body of an email that is sent via automation. It always came out as blank. But using {{Request Type.requestType.name}} as a smart value worked for me 🥳.