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

Is there a way to close an incident when associated alert is closed?

We use slack integration in order to notify/ack/close alerts via slack. It would be great if we could close an incident when its associated alert is closed from slack. is that possible?

1 answer

1 vote
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Mar 17, 2021

Hi @zahur don ,


There isn't a way to have the incident automatically be closed when an associated alert is closed. There can be several associated alerts for an incident, and more alerts can be associated to an incident after the incident is created.

We do have a feature request to be able to close the incident when all associated alerts for an incident are closed.




Hi @Samir ,

Does this also apply vice versa, i.e., when I close an incident, is it possible to make it also close the Associated Alerts altogether with Responder Alerts(that already are doing so). Or is there another approach for this workflow?

What I want to achieve is: 

  1. An external integration creates an (Associated) Alarm
  2. A Service Rule is triggered which creates an Incident(which itself creates a Responder Alert automatically)
  3. We resolve and close the Incident
  4. The Incident and all associated alerts(including Associated Alert(s), that triggered the Incident creation) get closed without us needing to manually close the Associated Alert(s) after already closing the Incident.
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 18, 2021

Hi @Veiko Jõõts ,


Currently it is not possible to have the associated alerts get closed when the incident is closed, although we do have a feature request for this!


What some users do is setup a webhook integration to trigger when the responder is closed, to trigger a script on AWS Lambda or something which will close the incident via API. You could also setup a similar solution using Opsgenie Edge Connector (OEC).




serge calderara
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Jul 01, 2021

hello @Veiko J , I need to do the same thing actually but seems a lot of logical approach are a feature request so far.

By the way I would be interrresting to know what is your process of solving a Incident.

What I mean and what is not clear is the use of the Responder Alert created at same time of the Incident which is a copy of the source Alert.

Do you work on the incident starting from the responder Alert, or the incident itself ?

What is the use of this responder alert exactly as based on docuementation is nothing else than pulling notification to responders member.

But the source Alert can do the same , why not working on the source Alert then ?

Simply because it can be off at some time automatically ?

Thanks for advise


Like Lina Massarwa likes this

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events