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

Automation to notify members quarterly based on a due date field

VVC

The team would set the "Due Date" field and status to recurring for specific issue type tickets. An automation would notify on quarterly basis every year that the report is due in 30 days.

Take for example, ABC-123 issue type with the "Due Date" is Oct 17 2014 and status equals recurring is currently set by the team. Note that the due date can be from the past date or in the future date as well and now it would be beneficial to be alerted on September 17th, December 18th, March 18th, and June 17th every year that the report is due in 30 days.

I have no luck in setting this up in JIRA Data Center Automation Rules and wanted to understand if this doable? Any suggestions with precise steps or screenshots will be greatly helpful.

Accepted answers

VVC

Thanks @Kalyan Sattaluri . It was my bad, as it is due to a typo. The days result is now displaying.

All comments

Kalyan Sattaluri_iinm1n

Hello @VVC

At a high level, requirements like these are solvable, so thats the good news... but we need details on what to do and how to solve.

For example, What is the field which hold if an issue is "recurring" or not?

Also quarterly, is it per calendar basis or based on due date?

So, take the example you have given of Due date as Oct 17 2014, when is the next notification you expect to see?

Please think through this example's specifics and share details around it, else we cannot provide suggestions.

Also, Please share what you have so far so community can help..

VVC

Hello @Kalyan Sattaluri

Thanks for looking into my question and I will try answering your questions.

1) Condition: Issue status = recurring and "due date" = 30d

2) Notification to be sent Quarterly based on the due date field that is already set on the ticket and when it is due in 30 days

3) There are a bunch of tickets with recurring status and due date published with either a past or a future date.

4) Automation should be able to trace each ticket with the ststus field set to recurring and when it is due in 30 days then trigger an email notification to the team on quarterly basis every year.

For example, ABC-123 ticket has a due date set to a past date as Oct 17, 2014. So the notification should trigger quarterly like starting on September 17th 2024, December 18th 2024, March 18th 2025, and June 17th 2025, September 17th 2025, December 18th 2025 and continue every year until that ticket is moved out of recurring in the status field.

Kalyan Sattaluri_iinm1n

TY @VVC

I think I understand requirement now.

Can I suggest below steps to know if our approach will work. We will test will an issue for now to check syntax and we can set up recurring schedule afterwards. Start with:

Trigger = scheduled with JQL = key=ABCD-1234 (uncheck the box which says )
Log {{Due date}}
Log: {{now.format("YYYY")}}-{{Due date.toDate.format("MM-dd")}}
Create Variable => newdueDate = {{now.format("YYYY")}}-{{Due date.toDate.format("MM-dd")}}
Log statement: {{now.diff(newdueDate.toDate).days}}

Below is the explanation:

First 2 steps are self explanatory,
in third, We are logging reformatted due date (date to that of this year),
In fourth, we are storing reformatted date in a variable,
in fifth, we are doing a diff against current date.

If we can get the fifth step to get you the days, then we can check if this diff is 30 or 120 or 210 days and if so, we can send email...

if above works, you will check your Trigger JQL to run daily and JQL => status = recurring

Hope it helps, please try and share your feedback, screenshots of your rule/audit log will help. Thanks!

Kalyan Sattaluri_iinm1n

Actually, I havent fully thought through the If conditions on when to send notifications, that is should be 30/120/210 or what... but please go upto step 5 to get the diff.

And we can evaluate correct logic tomorrow when we can think deeply. sorry have to rush now.

VVC

Looks like, we're getting close.

Applied the change that you have recommended and looks like that did the trick. I tried a few changes on the last component in the Automation Rule but the diff value is still failing.

Finally, instead of {{now.format("YYYY")}}-{{Date Needed By.toDate.format("MM-dd")}} , use, {{now.format("YYYY")}}-{{Date Needed By.format("MM-dd")}}

FYI - Date Needed By custom field

Date Needed By custom field context.png

Kalyan Sattaluri_iinm1n

hello, i am going to continue posting in other comment so discussion is together for future reference..

VVC

Thanks @Kalyan Sattaluri . It was my bad, as it is due to a typo. The days result is now displaying.

Kalyan Sattaluri_iinm1n

Awesome. Now I need some time to think through the logic to implement.. Basically I am thinking of doing brute force if checks on the date but need some time to think it through... I will update the post once I think through few scenarios..

Welcome!

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

Quick Links

Find more posts tagged with

server

jira

jira-server

jira-data-center

data-center