{{#Lookupissues}} via email automation not working

[Darwin Fernandez]

Hi there, 

I am trying to have an automation generate an email notification when an issue is created by using the following:

''

Hello!

The following ticket has been created:

<table>
<tr>
<th>Issue Key</th>
<th>Summary</th>
<th>Term Date</th>
</tr>

{{#lookupIssues}}

<tr>
<td><a href="{{url}}">{{Issue.key}}</a></td>
<td>{{Issue.summary}}</td>
<td>{{Issue.Effective End Date & Time.shortDateTime}}</td>
</tr>
{{/}}
</table>

Thanks,

''

-When i trigger the automation, i get the result below which contains no actual tickets:

''

Hello!

The following ticket has been created:

Issue Key	Summary	Term Date

Thanks,

''

-What am i doing wrong?

[Trudy Claspill]

Hello @Darwin Fernandez 

Try removing the "issue." portion of each smart value.

[Darwin Fernandez]

Hi Trudy! Thanks for your answer. I tried this, but the result stays the same.

[Trudy Claspill]

Can you show us the details of your rule?

Did you confirm that your Lookup Issues action is actually getting any results?

[Darwin Fernandez]

Here are the details, i have it as a manual trigger so that i can test it

Trigger 
Manual Trigger

Condition
If: Issue matches JQL:

cf[13100] = "custom field name"

Action

The code in the action is

<table>
<tr>
<th>Issue Key</th>
<th>Summary</th>
<th>Term Date</th>
</tr>

{{#lookupIssues}}

<tr>
<td><a href="{{url}}">{{Issue.key}}</a></td>
<td>{{Issue.summary}}</td>
<td>{{Issue.Effective End Date & Time.shortDateTime}}</td>
</tr>
{{/}}
</table>

How do i verify that the {{#lookupIssues}} is getting results? Based on what i shared I don't think that it is.

[Trudy Claspill]

When you do not use a manual trigger, what is the trigger for the rule? In your original post you said you are wanting to generate an email when an issue is created. In that case your trigger should be "Issue Created", and there is no need for the trying to put a table into the email because there will be only one issue to include, and no need to use the {{#lookupIssues}} {{/}} encoding.

[Darwin Fernandez]

the original trigger is issue created, but i think i am missing the JQL code after the table. That seems to resolve it.