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

Delaying incident creation

We are trying to use OpsGenie to manage alerts in our command centre, but I'm having issues with the automatic incident creation.

Ideal solution:

  • alert comes in
  • more alerts for the same issue arrive, and causes the count to increase
  • no notification takes place unless the de-duplication threshold is passed
  • If the threshold is not passed and no new alerts within the auto-close time, the alert is closed without notification and without incident being created.
  • if the de-dup threshold is passed, notification and incident rules are fired causing teams to be notified and incident to be created.

This will enable the team to manage incidents and not get overwhelmed by alerts, and ensure consistent incident creation. It will also avoid unnecessary incident creation for an alert that closes before notification takes place.


I found an open issue for this, please go and upvote it:


1 answer

1 vote
Rafael Meira
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Nov 25, 2022

Hey Nicki, thank you for all your explanation and also to put yourself already for the Feature Request.

Unfortunately, we don't have these features adjusted as you currently want, which is why we the feature request was indeed opened.

Once we have more information/updates you will receive a notification as you are already in this Feature request.

Best of luck,

Thank you.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events