Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

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.

Deleted user Avatar
Deleted user

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.

Atlassian Community about banner
Community Members
Community Events
Community Groups

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
AUG Leaders

Atlassian Community Events