Sum Up all affected Issue (Automation)

Leena Pratheepan

Hello everybody,

I have a rule that says that when version is updated, the assignee and owner (team leader) of the Issues with the updated version  must be informed.

By itself the rule works. Problem I get 30 mails each issue when a vision is updated.

How can I change the rule so that it summarizes the issues affected ( lookUpIssue) and avoids when assignee and owner are the same people, not notified twice.

 

Thank you for your help.

 

Bill Sheboy

Hi @Leena Pratheepan 

Please try using the Lookup Issues action instead of a branch: https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Lookup-issues

You could use JQL to find the issues in the updated version, and then send a single email listing all of them:

• trigger: version updated:
• action: lookup issues with JQL to find the issues in that version
• action: send email

Alternatively...let's say there are different owners for different issues.  A similar rule can solve that by iterating over the distinct assignees, like this:

• trigger: version updated:
• action: lookup issues with JQL to find the issues in that version
• advanced branch: on {{lookupIssues.assignee.distinct}}
  • action: lookup issues with JQL, adding a condition to match the branched variable for assignee
  • action: send the email

And if there are issues with no assignee, you may need a couple of extra steps to test/email for that one to inform the project lead.

Please try that, and let me know if you need more details.

Kind regards,
Bill