Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Disable notification upon priority increase

For an open incident when the priority is increased (e.g. from P3 to P1), the responder alert will restart. In the logs of the responder alert you see this message:
"Alert priority has been updated to P1 via system (Previous priority was P3). Will stop ongoing escalations and notification rule steps, and restart the notification flow as if the alert is newly created now."

For our use case, if the alert is acknowledged once when it was in P3 is enough. For the person handling the incident it is annoying to get a call for every priority increase.

Is there any way to turn this off or have a workaround for it?

I was checking the policy section and it doesn't really help. The only way I see so far is to supress notifications of P1 or P2 alerts. But that's obviously far from ideal. Any ideas?

Thanks for the help!

1 answer

0 votes

Hi Carsten!

 

It's not possible (at this time) to disable the reevaluation of the various aspects of the notification flow when the priority is increased - this is the default behavior, and there's not a way to turn it off.

 

In general, upgrading the priority is usually recommended when the alert itself needs to behave in a different way - to use a different escalation, or to notify different team members in a different schedule. If the alert is intended to continue to be responded to by the same user, and has already been acknowledged by that user, we would recommend not upgrading the priority at all. 

 

I have, however, entered in an internal feature request for this - the reference id for that request is: OGS-3717. I can't guarantee that this is something that we will be adding to the product, but I've added your feedback to the request's notes, and our product team will evaluate it.

 

Hopefully that helps to answer your questions, but please let me know if there's anything else I can assist with. Thanks!

 

Justin

Hello Justin,

thanks for you answer.

My question was really in regards to the responder alerts, not alerts in general. In our case, we create incidents automatically depending on other alerts that are coming in.
Then, there is one person managing the incident and it is kind of annoying that with every priority upgrade he/she gets another notification/call.

Thanks for filing the feature request!

KR Carsten

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PERMISSIONS LEVEL
Site Admin
TAGS
Community showcase
Published in Opsgenie

How do I use Zebrium + Opsgenie for Root Cause Analysis (RCA)?

This article was co-authored by Gavin Cohen of Zebrium. Zebrium has a bi-directional integration with Opsgenie and is a machine learning solution for RCA.  We all know the drill. 💤 You'r...

324 views 0 3
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you