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.
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!
Come for the products,
stay for the community
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Escalation not triggering
Kindly assist, set up an escalation process, but does not get triggered. Only the first notification for the team. Alert was not acknowledged.
Does Team escalation require Integration set-up within the Team? We don't have a Team specific Integration, we use only Global Policies pointing to a Team.
2 answers
1 accepted
Hi @Donny Gison ,
Glad you figured this out, but I still wanted to share with the Community what the issue is since we come across this quite frequently.
If you review the alert's activity logs, you'll see this team's routing rule is sending alerts directly to the on-call schedule - essentially skipping over the escalation entirely:
The quick and easy fix is selecting the team's escalation in the default routing rule - which can manage notifying the on-call users of a schedule, and others if no action is taken on the alert:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.