nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

JSM Automation - nested lookupissues inside FOR EACH sends duplicate emails

Alik Levin

Overarching goal - send last month's report to customer.

Logic:

1. Get last months JSM tickets

2. Iterate for each related Organization associated with the ticket.

3. Filter tickets for current Organization

4. Inside the branch send email - summary of tickets for each Organization.

5. The email content generates just fine!

6. PROBLEM - the automation sends same amount of emails as the number of tickets for that org. For example, if I have Org A with 1 ticket, Org B with with 2 tickets, and Org C with 3 tickets, I am getting 1 email for Org A, 2 identical emails for Org B, and 3 identical emails for Org C.

7. Problem of dups disappears when I change Advanced Branching Smart Value

from:

to:

How to fix and avoid getting duplicate emails when using {{lookupIssues.Organizations.flatten.distinct}}?

Reasoning for why I cannot just fall back to {{lookupIssues.Organizations.flatten.name.distinct}} which works fine, no dups: I also need the Org's Id and I don't see the way to extract it when iterating over Org's name, I need to iterate over Org's object.

Thanks!

Accepted answers

All comments

Bill Sheboy

Hi @Alik Levin

Without seeing the specifics of your entire rule and audit log details...

I suspect the problem is the flatten and distinct functions are having difficulty because Organizations is an object and has several attributes...rather than a single value.

Thus a workaround would be to use advanced branch over a single, flattened attribute, such as the Organization ID, and then within the branch, repeat the lookup and add the branch variable (i.e., the ID) to the JQL:

UPDATE: It appears the Organizations smart value is one which is loaded just-in-time, and thus cannot be used as I first suggested. I confirmed this with testing both my original and the revised approach. Either the entire object must be referenced and it will be looked up later; or all the orgs must be extracted into a created variable, and then parsed into a list for iteration. The first approach is easier:

{{lookupIssues.Organizations.flatten.distinct}}

and within the branch, perhaps using the branch variable named varOneOrg added to the JQL:

AND Organization = {{varOneOrg.id}}

Kind regards,
Bill

Alik Levin

Screenshot 2025-12-07 at 6.46.47 PM.png

Screenshot 2025-12-07 at 6.48.35 PM.png

Alik Levin

Downstream I have Send Customized email with this snippet that builds the content:

{{#lookupIssues}}
<tr>
<td><a href="{{url}}">{{key}}</a></td>
<td>{{summary}}</td>
<td>{{customfield_10144.asCurrency()}}</td>
</tr>
{{/lookupIssues}}

Bill Sheboy

Hi @Alik Levin

Thanks for your rule image, and after testing I found Organizations appears to be one of the smart values loaded just-in-time, the same as subtasks and issuelinks. Thus it cannot evaluate fast enough for the id to be parsed out before the flatten and distinct happened in my original suggestion.

My original suggestion would only work if all of the orgs were first parsed into a created variable...forcing their evaluation. And then flattened and examined with distinct. As that seems unnecessary as the name and id are not needed until later, using the object directly in the branch seems to work.

For the updates you show, are they working as you expected?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management