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.
1 answer
1 accepted
Hi @Giovanni Tirloni ,
Closest thing to that use case is a Notification Policy which can restart notifications after X-time for high priority alerts.
These can be configured under a team's Policies tab, and that policy might look something like this:
Hi @Giovanni Tirloni ,
within escalation rules you can restart an escalation path and check the option to reset the acknowledge state in each restart.
So you can create a new routing rule and escalation for your specific cases.
^ What @Stefan Draber mentioned above is also another option.
I should have mentioned earlier that restarting notifications through a Notification Policy will also revert the ack'd state too:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.