Automation: How to fetch name list of issues with specific status

Question

I'm inside the content field of Send Email action. I've tried several ways but not working at all, here is the pseudo code: {{#project.issue}}{{.}} {{#if(equals(issue.status.name, "Pending"))}} {{#issue.subtasks}}{{summary}}{{^last}}
{{/}}{{/}} {{/}} {{/}} Hoped this way could fetch "name list of subtasks of all issues of this project", anyone could help?

Bill Sheboy · Answer

Thanks for clarifying.

If your issues are all assigned to a fixVersion you could find them with JQL, using those functions.  For example, https://support.atlassian.com/jira-software-cloud/docs/jql-functions/#earliestUnreleasedVersion--  And then use the lookup issues action to gather them for reporting: https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Lookup-issues

And / or if you want this message send after the Jira version is Released, the rule could be triggered by that to send the message, iterating over the issues in the version: https://support.atlassian.com/cloud-automation/docs/jira-automation-triggers/#Version-created--updated--released

Or, you could use JQL which only returns the issues of your type (or their parent) and that status and then produce that list using the lookup issues action, as noted earlier.

Perhaps try one of those ways if they align to your reporting need.

Devon Chan_w3m7r0 · Answer

My project have 100+ issues, but only got 30-ish in a single status. So if JQL or smart values can narrow it down to that status, should be fine in theory.

I'm trying to produce Release Notes or reports based on the JIRA tasks and subtasks. I've tried some plugins and also the native export function, but those are all so bulky and not providing this simple list:

Issue 1
- Subtask 1
- Subtask 2
Issue 2
- Subtask 3
- Subtask 4

Bill Sheboy · Answer

Please re-read what I posted above, including...

Rules get issues from the trigger, actions, and conditions.  Your rule has no trigger yet, so you would need to select one for the community to know how to help with your rule.

Rules can process, at most, 100 issues.  Does your project have more than 100 issues?

If your rule used JQL to gather the issues, and there were <= 100 issues, you could format a resulting email as you show.  However the expression you show in the email action would not do that.

What problem are you trying to solve?  That is, "why" do this?  Knowing that may help the community to offer suggestions to solve that problem.