Suggested improvements

• Being able to use a smart value like: lookupIssues.customfield.average / lookupIssues.customfield.sum }}Would highly increase the use of {{lookupIssues smart value as this would allow us to access various custom fields from different tickets.
• Support TimeSpent in Jira Automation Lookup
• Cannot use max() with list of Objects
• I was testing lookup issues in Jira automation when I found that priority lookup is not available in Jira automation. As it is one of the most essential parts of the issues, kindly add this as soon as possible.
• lookup issues function to be able to access the worklog smart value.
• From the resulting issue list, the following issue properties are available to use (custom fields aren't available):

• • {{ key}} - Returns the issue key

• • {{ url}} - Returns the issue url

• • {{summary}} - Returns the issue summary

• • {{assignee.displayName}} -  Returns the assignee

• • {{reporter.displayName}} -  Returns the reporter

• • {{status }}- Returns the status

• • {{issueType}} - Returns the issue type

• • {{resolution}} - Returns the resolution status

• • {{fixVersion}} - Returns the fix version

• • {{created}} - Returns the date the issue was created

• • {{updated}} - Returns the date the issue was updated

• • {{Story Points}} - Returns the story points for the issue (classic Jira Software)

• • {{Story point estimate}} - Returns the story points for the issue (next-gen Jira Software). Learn more about using smart values with numbers.

Refer to the article for more information: https://support.atlassian.com/jira-software-cloud/docs/automation-actions/#Automationactions-Lookupissues