{{issue.parent.Epic Name}} returns no value with a {{#lookupIssues}}

[Mario GELES]

Hi Community, 

I am trying to create an automation that will send an email with some information regarding a number of tickets. 

So I'm using a manual trigger for my tests and a "LookupIssues" action (with a JQL query that searches through all the tickets of my project) and then a "send email" action. 

In the email I use the following smartvalues :

{{#lookupIssues}}
{{project.name}}
{{issueType.name}}
{{key}}
{{summary}}
{{issue.parent.Epic Name}}
{{/}}

All the smartvalues are working except the {{issue.parent.Epic Name}} smartvalue that return no value. 

However, in my log action the {{issue.parent.Epic Name}} smartvalue returns the correct value. So it seems that the syntax is right. 

Did I miss something? Does {{issue.parent.Epic Name}} smartvalue work with {{#lookupIssues}}{{/}} smartvalue? 

Thank you for your help!

[Nic Brough -Adaptavist-]

A field configuration defines several things about a field used in a specific project and issue type.  These things include renderer, whether it's mandatory and whether it is hidden.

For a field to appear, as well as not being hidden in the field config, it must have the right context (on the main list of custom fields), and be on the "screen" you are using for the issue.

Boards are different again.  A field must be available as above, but you probably need to add it to the board display as well.