Is this possible with automation?

[donhames]

As I study the power that Atlassian automation has, it seems that every rule starts off with a single issue. Is there a way to have a JQL filter to limit the scope of the automation and then iterate over each issue in the filter to perform some action(s)?

It would be ideal if I could write a JQL filter to select the issues and then go through them 1 by 1 until the end. This could be used to automate verifying that the correct fields are populated, and if not, put in the value. That is the first and primary use I can think of processing a group of issues in a single automation rule.

Any ideas on how to do this, or is it even possible? I can always fall back to ScriptRunner or Python, but I prefer it in automation rules, which can be triggered within Jira.

Thanks, as always, for your input and suggestions.

[Dave Liao]

Hi @donhames ! You're in luck; this is possible.

Consider a rule like this:

• Trigger = Scheduled (on a timed basis, like daily)
  • As part of the Trigger, JQL search for specific Issues, then iterate on each found Issue.

To learn more, review the KB article on Automation Triggers: https://support.atlassian.com/cloud-automation/docs/jira-automation-triggers/

FYI I moved this question out from Enterprise into the Jira Software section since it's pretty much a Jira question.

[Kuan Yi Ming _ServiceRocket_]

Hi @donhames,

It's possible to run this using a scheduled behavior as suggested by @Dave Liao. If you'd like another way to trigger this automation (e.g. whenever an issue in your JQL filter is modified), you can implement a different set of conditions:

1. Condition - JQL condition - use the JQL filter you have to check if the current issue is part of the same JQL filter

2. Branch rule - type of related issue - use the JQL filter, then implement any actions you need to do for all JQL filters in the issue within the branch

Hope this helps!

-yiming