Jira Automation to forward epic statuses

[jeelani Karim]

• Trigger: Scheduled 
• Condition: Issue type as Epic
• Action: Lookup issues > query to check status as Closed
• Action: Lookup issues > query to check status as Review
• Action: Lookup issues > query to check status as Ready
• Action: Send Email> store {{lookupIssues.flter("status = 'Closed'"). size}}

[Tomislav Tobijas · Accepted solution]

Hi @jeelani Karim ,

I might be wrong here (if I am, I hope someone will correct me), but I don't think you can use .filter() function within {{lookupIssues}} smart value 👀

If you're using Jira automation 9.0 (as this seems to be Jira on-prem), you could probably use variables to store the response from each Lookup action.

Basically, you could build the following automation:

• Trigger: as-is
• Condition: as-is
• Action: Lookup issues > first query
• Action: Create variable > store {{lookupissues.size}}
• Action: Lookup issues > second query
• Action: Create variable > store {{lookupissues.size}}
• ...

This could probably be optimized a bit more, but it might be a good starting point.

With the current setup, when you are in the last action, Send email, you're only referencing the last result from the Lookup issues action, meaning the result of the query 

Status = "READY FOR REVIEW" and "planning increment" ~ CCB-25Q3

Here are also some relevant materials related to dynamic searches and Lookup issues action:

• AUTO-1807: LookUpIssues list does not support using filters (like fields, vars , etc) in Automation Smart Value 
• AUTO-490: Automation Smart value iterations don't have access to the original issue variable 
• Automation concepts -- Dynamic searches within a list 

Hope this helps.

Cheers,
Tobi

[jeelani Karim]

Thanks @Tomislav Tobijas : This worked for me and i could populate the right counts