Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Automation email


I am still new to using JSM and trying to learn all the different automation emails that I can send. I currently have a reminder email that will go out to users when the status of their issue has been in the "Waiting on Customer" status for more than 24 hours. This gets send every 24 hours until the issue reaches 5 days and then the ticket will automatically close if it is still in the "Waiting on Customer" status. Here is what I would like to do if at all possible.

I would like the first reminder email to be sent twice. Then one more reminder stating that the ticket is going to be closed if you don't take action. Then have it close on the 5th day.

Example: Issue goes into "waiting on customer" on Monday. Tuesday comes and it is still in that status, so a reminder email goes out, the same thing on Wednesday. On Thursday, I would like a final notice email to go out that says it will be closed if you don't take action. Then on Friday, the ticket closes automatically due to no activity.

Like I said, I have the first part figured out and the auto close email works just fine. Do I need to create a different automation rule for the other email to go out or can I include it in the first email rule and if so, what would the conditions be?

2 answers

0 votes
Joseph Chung Yin
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Oct 10, 2023 • edited

@Jeremy Tatro -

Based on my understanding all automation rule on sending out email notifications are custom to your specific JSM project, so you should work with each project's Administrator for assistance on rule configuration and setup.

The out of the box notifications from any JSM project can be found by accessing each project's Project's "Project settings" >> "Customer notfications" UI (see example link below).  It contains all the notification events out of the box which can be enabled/disabled.

https://<yoursite><your project key>/settings/customer-notifications

For Automation for Jira - Here are the links that you can learn about -

One thought is for you to setup different SLAs for your JSM project, then you can use the the SLA breached triggering event to create your custom automation rule to send out custom email notification + auto close out the issue actions.  On the other hand, if you don't want to go with the SLA route, then you can setup a "Scheduled" triggering event in your automation rule design and create condition to test against the "Updated"/"Created" fields values to determine if an issue has not been updated since issue creation, afterward design your custom email notification and auto-closed issue action.

Hope this helps.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Technology Applications Team

Viasat Inc.

0 votes
Frederic Chartrand
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.
Oct 10, 2023 • edited

Hi @Jeremy Tatro 

Each time I have to set something like that in place, I use SLA in my project(s).

You could have one SLA for 24 hours, one for 48 hours, one for 96 hours and one for 120 hours. (You need one SLA for each timeframe, setting up more than one goal in a SLA doesn't work).

Ex. : 

  • SLA - Waiting for customer - First notice
  • SLA - Waiting for customer - Second notice
  • SLA - Waiting for customer - Last notice
  • SLA - Waiting for customer - Auto-close

The SLA would be triggered by the status "Waiting for customer" and would end when the status change to something else (the linked statuses in your workflow).

And you'd have an automation rule for each SLA. The trigger of this rule would be "When SLA breached" and you choose your SLA and you send an email (and for the last one, you.  transition your issue and send an email)

This way, the trigger is exactly 24 hours or 48 hours etc. Your rule don't need to scan all issues because it's the SLA that triggers it.

Works flawlessly for me.

Hope it helps


Ref. : Create service level agreements (SLAs) to manage goals | Jira Service Management Cloud | Atlassian Support


Have a nice day.

Frederic Chartrand - FMX Solutions - Gold Solution Partner

I will give that a try and let you know how it pans out. Thank you for the guidance. 

Like Frederic Chartrand likes this

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events