My outing rules are not working from opsgenie-- If I ackw alert in opsgenie it is not adding comment
Asked by anees:

I am on JSM cloud and have Opsgenie installed in it.

I am currently exploring Opsgenie. I have performed integration between Opsgenie and JSM,

when i add comment in JSM ticket, it is getting added to Opsgenie alert.

But when i ackw alert is Opsgenie it should ideally add comment in JSM ticket stating "so and so user ackw alert" which is not happening.

do I need any further settings from JSM side as well?


Answers:
author: anees
body: Sure Nick. Thanks you for your response.


author: anees
body: Hi Nick,

Thanks for your immediate response on this.

[This other Community article](https://community.atlassian.com/t5/Opsgenie-articles/Opsgenie-Alerts-Not-Creating-Jira-Jira-Service-Management-Issues/ba-p/1563628) whatever configurations are shown in this article I don't see them in my JSM,(may be because I am on new JSM framework).

Secondly I have updated point 2 which you have highlighted. but my question is " is point 2 mandatory action to do"? if we uncheck below option then I don't need to do point 2 and point 3 right. Please confirm the same

##### Create and update requests with Opsgenie alerts that are created by other integrations {#toc-hId--1649722920}

comments: author: Nick H
body: I think it's all dependent on your workflow. The integration can send updates to JSM issues for two different use cases; for alerts created by JSM issues, and for alerts that were created by other integrations / create JSM issues.

1 - If your JSM issues are creating Opsgenie alerts, then the **Outgoing automation rules** section manages the actions taken on the alerts that will reflect back in JSM:

![ack4.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/199846i5353B4E8EC2A8BCD/image-size/large?v=v2&px=999 "ack4.jpg")

2 - If your Opsgenie alerts are creating JSM issues, then you need to manage the actions taken on alerts that reflect in the JSM issues here under the **Create and update requests with Opsgenie alerts that are created by other integrations**section:

![ack 5.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/199848i8D13FE231F5A99DE/image-size/large?v=v2&px=999 "ack 5.jpg")![ack3.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/199847iC437061AEE17136A/image-size/large?v=v2&px=999 "ack3.jpg")


author: Nick H
body: Hi [@anees](/t5/user/viewprofilepage/user-id/4528265) ,

[This other Community article](https://community.atlassian.com/t5/Opsgenie-articles/Opsgenie-Alerts-Not-Creating-Jira-Jira-Service-Management-Issues/ba-p/1563628) may help with your issue. Although it's related to issues not being created, it's still relevant to comments not being added back to an issue.

If you are using the older JSM framework, you can manage the actions being sent to JSM here:

![ack1.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/199833iE1760EEE8A37AE7E/image-size/large?v=v2&px=999 "ack1.jpg")

If you are using the new JSM framework, you can manage those actions here:

![ack2.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/199835iB9D8024D6DC7AF9E/image-size/large?v=v2&px=999 "ack2.jpg")![ack3.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/199834i979EA0950EDDD671/image-size/large?v=v2&px=999 "ack3.jpg")


Tags: jira-service-management-cloud