Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

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

arjun
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 10, 2024

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:

  1. schedule everyday 9AM
  2. Lookup issue in current Sprint which are not updated in last 3 days
  3. If lookup size > 0 then advance branching with {{lookupIssues.assignee.distinct}} and assign to distinctAssignee
  4. then lookup issue same as 2 with assignee equals distinctAssignee
  5. 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

2 answers

1 accepted

3 votes
Answer accepted
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 10, 2024

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

arjun
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 10, 2024

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

Like Bill Sheboy likes this
0 votes
Kalyan Sattaluri
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 10, 2024

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

Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 10, 2024

@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.

Like # people like this
Kalyan Sattaluri February 10, 2024

...x

Kalyan Sattaluri
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 10, 2024

Thanks Bill, Def should have paid more attention!

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events