It's possible to close an alert in opsgenie by resolving the issue which triggered to open?
Asked by Bruno Brendel:

I need to close alerts in Opsgenie, but it is not scalable for my team to access two platforms to resolve an issue.

Is there a way to automatically close the alert in Opsgenie every time an issue, which triggered an alert in Opsgenie, is closed in JSM?


Answers:
author: Fabian Lim
body: Hi [@Bruno Brendel](/t5/user/viewprofilepage/user-id/5254587)

Welcome to the community!

Yes, it's possible. Details can be found here: <https://support.atlassian.com/opsgenie/docs/the-integration-framework/>

comments: author: Bruno Brendel
body: Hey Fabian, thanks for your response.

I'm having trouble with that because i have configured an incoming rule to close the alert but the alert doesn't close when the issue goes to status conclu?do or cancelado.

![Captura de Tela 2023-06-28 a?s 13.52.36.png](https://community.atlassian.com/t5/image/serverpage/image-id/265576i75C08FD89FC3C3C4/image-size/large?v=v2&px=999 "Captura de Tela 2023-06-28 a?s 13.52.36.png")

When i create a issue on JSM the alert is created normally on Opsgenie


author: Fabian Lim
body: Hi [@Bruno Brendel](/t5/user/viewprofilepage/user-id/5254587)

I noticed that sometimes the updated event doesn't trigger when status change. Can you try adding editing the ticket (i.e. change any field after the ticket is transitioned) and see if the alert closes?


author: Bruno Brendel
body: Hey Fabian, thanks for your response.

I finally discovered what is happening.

When I create an issue on Jira with the issue type "incidente," an alert is generated.

However, when I move a ticket to "conclu?do", I am using status, eventType, and issueType as filters to close the alert.

The problem that was occurring is that when I move the ticket to "conclu?do," Opsgenie is not reading all the parameters of the filter to close the alert. It stops at "issueType = incidente" and then ignores the rest, leading to the creation of a new alert.

As a solution, I added one more parameter to create an alert.

![Captura de Tela 2023-07-05 a?s 09.58.57.png](https://community.atlassian.com/t5/image/serverpage/image-id/266867i36A19838DB07321B/image-dimensions/414x179?v=v2 "Captura de Tela 2023-07-05 a?s 09.58.57.png")

After that, the alerts start closing when the ticket is moved to "conclu?do"


author: Rosa M Fossi
body: [@Bruno Brendel](/t5/user/viewprofilepage/user-id/5254587) Glad to hear you where able to gets this fixed! If my response below helped you get there, don't forget to upvote ?


author: Fabian Lim
body: [@Bruno Brendel](/t5/user/viewprofilepage/user-id/5254587)

please set the ticket to resolved when you have a chance.


author: Rosa M Fossi
body: Bienvenido [@Bruno Brendel](/t5/user/viewprofilepage/user-id/5254587)

I'm not certain if this might affect it, but I tested on my own account and none of my "close alert" rules contain issueType. Try removing them and test again.

You might also want to make sure you have matching cases... (**I** ncidente vs. **i**ncidente)

![issueType-in-Rule.png](https://community.atlassian.com/t5/image/serverpage/image-id/266437iAF2AB534994AA57E/image-size/large?v=v2&px=999 "issueType-in-Rule.png")

<br />

<br />

If those suggestions do nott work, can you share a screenshot of the edit screen for *fechar no jsm \| Fecha no opsgenie* Rule?