I wanted to send each assignee an email to update the issue which are not updated in last 3 days. I referred the similar approach as mentioned here If I deduce my steps it will be something like: * schedule everyday 9AM * Lookup issue in current Sprint which are not updated in last 3 days * If lookup size > 0 then advance branching with {{lookupIssues.assignee.distinct}} and assign to distinctAssignee * then lookup issue same as 2 with assignee equals distinctAssignee * If lookup size > 0 then send to distinctAssignee.emailAddress Please find the below screenshot of my implementation. It is currently sending multipl emails to the same assignee to be precise x times x being the lookupissue size before branching The difference between this image and the mentioned link is the branch which seems to starts before for in my case. I am stuck for around 1 month Its kind of urgent Any help is appreciated

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; } } }

I am trying to send one email to each user who have not updated their issue in last 3 days

arjun_j7g2wa

I wanted to send each assignee an email to update the issue which are not updated in last 3 days. I referred the similar approach as mentioned here

If I deduce my steps it will be something like:

schedule everyday 9AM
Lookup issue in current Sprint which are not updated in last 3 days
If lookup size > 0 then advance branching with {{lookupIssues.assignee.distinct}} and assign to distinctAssignee
then lookup issue same as 2 with assignee equals distinctAssignee
If lookup size > 0 then send to distinctAssignee.emailAddress

Please find the below screenshot of my implementation. It is currently sending multipl emails to the same assignee to be precise x times x being the lookupissue size before branching

Screenshot 2024-02-10 at 4.22.49 PM.png

The difference between this image and the mentioned link is the branch which seems to starts before for in my case.

I am stuck for around 1 month Its kind of urgent Any help is appreciated

Accepted answers

Bill Sheboy

Hi @arjun -- Welcome to the Atlassian Community!

Please check your Scheduled Trigger, as it should have no JQL. Otherwise it will loop for each user multiple times.

The rule uses the Lookup Issues action and the branch to iterate over the users, and not the one from the trigger.

I also noted a typo in your Send Email Action: there is an extra space after the period and before the emailAddress smart value. I recommend removing that: smart values are name, spacing, and case-sensitive, and so that error could eventually cause problems.

Kind regards,
Bill

All comments

Bill Sheboy

Hi @arjun -- Welcome to the Atlassian Community!

Please check your Scheduled Trigger, as it should have no JQL. Otherwise it will loop for each user multiple times.

The rule uses the Lookup Issues action and the branch to iterate over the users, and not the one from the trigger.

Kind regards,
Bill

Kalyan Sattaluri_iinm1n

Hello @arjun Can you confirm that in your first step of scheduled trigger, you have selected "Process all issues produced.." checkbox

Bill Sheboy

@Kalyan Sattaluri for this type of rule, the scheduled trigger should have no JQL, and thus that checkbox option has no meaning.

Please re-read the original question / symptom and the linked article the poster provided to learn more about such automation rules.

Kalyan Sattaluri

...x

Kalyan Sattaluri_iinm1n

Thanks Bill, Def should have paid more attention!

arjun_j7g2wa

Thanks a lot. The issue was because of scheduled Trigger containing JQL query.

And there was no extra space in the Send Email Action it just visual issue.

Thanks

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

automation