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
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
We see there is a "notify next user (in rotation)" but this isn't quite what we are looking for.
For example, say we want the primary rotation to be a senior developer role and the backup rotation to be a junior developer role.
Senior Senior Senior (Primary rotation)
Junior Junior Junior (Backup rotation)
We want our escalation rule to first notify the senior developer. If the senior developer doesn't acknowledge then we want to notify the junior developer.
However, we don't want to put the senior developer in a rotation followed by a junior developer, this prevents us from using "notify next user (in rotation)." This would look like:
Senior Junior Senior (Primary rotation)
Junior Senior Junior (Backup rotation)
There is possibly another solution we can create to achieve this maybe?
Possible solution: I believe the best possible way is to create a primary and backup schedule, if not acknowledged by first schedule, notify second schedule.
Hi @Blake_Wright ,
It's not possible to notify a specific rotation of a schedule - FYI @Andrew Laden
When an escalation rule is set to notify the on-call user(s) in a schedule, it will notify whoever is on-call determined by the red vertical line - regardless of the rotation(s).
So for this use case, you may want to break each rotation into its own individual schedule like a Primary vs. Secondary (or Senior vs. Junior).
The first rule of the escalation would notify the on-call user(s) of the Senior schedule, and the second rule would notify the on-call user(s) of the Junior schedule: