Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
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

Priority for long running incidents

Long running incidents go through severity changes before it is ultimately resolved. The priorities might get bumped up in the early stages and then lowered as well.


The lowering of priorities happens when we are able to quickly restore the service levels for a few of the affected customers but it is going to take say, another 4 hours before it is resolved for everyone. Do you typically lower the priority at this point?

  • Why you should lower: to communicate to stakeholders and responders that the situation is improving and the problem is no longer as bad as it was sometime ago
  • Why you should not lower: the original severity of the problem is lost. Becomes very hard to find out "how many P2 incidents did we have this month" as final priority state might be might be much lower than peak priority



Log in or Sign up to comment
Community showcase
Published in Opsgenie

Leveraging Atlassian’s Opsgenie and AWS Cloudformation Registry to stay ahead of incidents

In the past, managing IT infrastructure was a hard job. It required a lot of manual effort and it was hard to keep track of all the necessary information (monitoring, scalability etc). Thankfully, as...

2,368 views 0 13
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