You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
In my previous position using a different CRM system, i was able to perform the following automation rule:
Step 1 - If a ticket is in "Waiting on Customer" status for more than 1 day, the customer gets an email notification
Step 2 - If after 2 days, they get a second notification
Step 3 - if after 3 days, the ticket is transitioned to our 24HR close status, with a corresponding email as well.
this sequence should be consecutive, and not repeating.
Although Jira has relatively extensive automation components, i am unable to find anything that closely resembles the above rule.
any suggestions or assistance is appreciated. Though I am not new to IT or ITSM based products, I am new to Jira itself
UPDATE: i was able to create something that seems to work using Legacy Automation, but had to create 3 separate rules. If possible i would like something cleaner
Thank you!!
Hi @Marc Blascak,
Welcome to Atlassian Community!
Have a look at the automation library, in it there is an automation called "Resolve issues due to inactivity" which you could use are your base for the rule you are looking for. In order to combine all three rules, schedule the rule to run every day and then add a branch that checks when the request was last updated.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
thanks for the detailed response! I will test this out and let you know how it goes.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.