LookupIssues not returning many fields when iterating list of tickets

[Jeff Wieland]

Firstly - I set up a Scheduled Task - every day at 9 - that part worked.

Secondly - I am using a Lookup JQL search and it worked - it gave me all matching tickets

The problem I am having, is, it returns the Key  - but wont return anything else.I am using the following to send the email - taking into account the loopupIssues tree, and it DOES return all ticket keys -- but it does not import any other fields.  I did try adding assignee into the mix and it DID work - so then I had Key and Assignee .. but cant figure out why I can not get any of the following, status/customer/ownership from fields.

[Bill Sheboy · Accepted solution]

Hi @Jeff Wieland -- Welcome to the Atlassian Community!

When inside the iterator for the lookup results, the issue prefix is not used.  For example:

{{#lookupIssues}}
* {{key}} -- {{summary}}
{{/}}

Kind regards,
Bill

[Jeff Wieland]

Thank you Bill! 4 hours of frustration with a "but it works everywhere else" not realizing you need to modify the "issue." prefix out of the smart values inside of an iteration statement! 

[Arkadiusz Wroblewski]

Hello and welcome to the Community @Jeff Wieland 

Also we had an incident related to lookup issues adding to answer from @Bill Sheboy 

Failure in Automation and In System itself are not good combination 😅

[Jeff Wieland]

Nothing beats when I tried to JQL the Scheduled task AND copy/paste the same reference for Lookup Issues -- turns out you end up in an infinity loop and my entire leadership team got 41 emails before I disabled the automation task -_-