-
Suggestion
-
Resolution: Unresolved
-
None
User Problem
In the current design, the JSM integration is only for Opsgenie Alerts and JSM issues syncing. However, the term, Incident, exists on both products for the similar objective, it makes more sense to have the synchronization between them.
Suggested Solutions
Please consider building the synchronization between the Incidents on JSM and Opsgenie, without further configurations with the Incident Rules and the Responder Alerts.
Current Workarounds
For JSM to Opsgenie
- Complete the JSM Cloud integration.
- Set up the Incident Rules on the associated teams to match the JSM issues that are created in the "Incident" Issue Type.
In this way, whenever a JSM Incident is created, an Opsgenie Alert and an Opsgenie Incident will be generated automatically.
For Opsgenie to JSM
- Configure the Action Filter on the JSM Cloud integration to only post the Responder Alerts, which are created by the Opsgenie Incident for the associated teams, to create an JSM issue in the "Incident" Issue Type.
In this way, whenever an Opsgenie Incident is created, Opsgenie will create the Responder Alert to the team who is listed as a Responder Team, and Opsgenie will post this alert data to create a JSM Incident accordingly.
- is related to
-
- Reviewing
-
- Under Consideration
[OPSGENIE-1274] As an admin, I expect the synchronization between the Incidents on JSM and Opsgenie
| Link | New: This issue is related to JSDCLOUD-14539 [ JSDCLOUD-14539 ] |
| Assignee | New: Kaushik Mitra [ 933bb4f01eab ] |
| Link | New: This issue is related to OPSGENIE-67 [ OPSGENIE-67 ] |
| Description |
Original:
h3. User Problem
In the current design, the JSM integration is only for Opsgenie Alerts and JSM issues syncing. However, the term, Incident, exists on both products for the similar objective, it makes more sense to have the synchronization between them. h3. Suggested Solutions Please consider building the synchronization between the Incidents on JSM and Opsgenie. h3. Current Workarounds h4. For JSM to Opsgenie # Complete the JSM Cloud integration. # Set up the Incident Rules on the associated teams to match the JSM issues that are created in the "Incident" Issue Type. In this way, whenever a JSM Incident is created, an Opsgenie Alert and an Opsgenie Incident will be generated automatically. h4. For Opsgenie to JSM # Configure the Action Filter on the JSM Cloud integration to only post the Responder Alerts, which are created by the Opsgenie Incident for the associated teams, to create an JSM issue in the "Incident" Issue Type. In this way, whenever an Opsgenie Incident is created, Opsgenie will create the Responder Alert to the team who is listed as a Responder Team, and Opsgenie will post this alert data to create a JSM Incident accordingly. |
New:
h3. User Problem
In the current design, the JSM integration is only for Opsgenie Alerts and JSM issues syncing. However, the term, Incident, exists on both products for the similar objective, it makes more sense to have the synchronization between them. h3. Suggested Solutions Please consider building the synchronization between the Incidents on JSM and Opsgenie, without further configurations with the Incident Rules and the Responder Alerts. h3. Current Workarounds h4. For JSM to Opsgenie # Complete the JSM Cloud integration. # Set up the Incident Rules on the associated teams to match the JSM issues that are created in the "Incident" Issue Type. In this way, whenever a JSM Incident is created, an Opsgenie Alert and an Opsgenie Incident will be generated automatically. h4. For Opsgenie to JSM # Configure the Action Filter on the JSM Cloud integration to only post the Responder Alerts, which are created by the Opsgenie Incident for the associated teams, to create an JSM issue in the "Incident" Issue Type. In this way, whenever an Opsgenie Incident is created, Opsgenie will create the Responder Alert to the team who is listed as a Responder Team, and Opsgenie will post this alert data to create a JSM Incident accordingly. |
| Description |
Original:
h3. User Problem
In the current design, the JSM integration is only for Opsgenie Alerts and JSM issues syncing. However, the term, Incident, exists on both products for the similar objective, it makes more sense to have the synchronization between them. h3. Suggested Solutions Please consider building the synchronization between the Incidents on JSM and Opsgenie. h3. Current Workarounds h4. For JSM to Opsgenie # Complete the JSM Cloud integration. # Set up the Incident Rules on the associated teams to match the JSM issues that are created in the "Incident" Issue Type. In this way, whenever a JSM Incident is created, an Opsgenie Alert and an Opsgenie Incident will be generated automatically. h4. For Opsgenie to JSM # Configure the Action Filter on the JSM Cloud integration to only post the Responder Alerts, which are created by the Opsgenie Incident for the associated teams, to create an JSM issue in the "Incident" Issue Type. In this way, whenever an Opsgenie Incident is created, Opsgenie will create the Responder Alert to the team who is listed as a Responder Team, and Opsgenie will post this alert data to create a JSM Incident accordingly. |
New:
h3. User Problem
In the current design, the JSM integration is only for Opsgenie Alerts and JSM issues syncing. However, the term, Incident, exists on both products for the similar objective, it makes more sense to have the synchronization between them. h3. Suggested Solutions Please consider building the synchronization between the Incidents on JSM and Opsgenie. h3. Current Workarounds h4. For JSM to Opsgenie # Complete the JSM Cloud integration. # Set up the Incident Rules on the associated teams to match the JSM issues that are created in the "Incident" Issue Type. In this way, whenever a JSM Incident is created, an Opsgenie Alert and an Opsgenie Incident will be generated automatically. h4. For Opsgenie to JSM # Configure the Action Filter on the JSM Cloud integration to only post the Responder Alerts, which are created by the Opsgenie Incident for the associated teams, to create an JSM issue in the "Incident" Issue Type. In this way, whenever an Opsgenie Incident is created, Opsgenie will create the Responder Alert to the team who is listed as a Responder Team, and Opsgenie will post this alert data to create a JSM Incident accordingly. |
| Description |
Original:
h3. User Problem
In the current design, the JSM integration is only for Opsgenie Alerts and JSM issues syncing. However, the term, Incident, exists on both products for the similar objective, it makes more sense to have the synchronization between them. h3. Suggested Solutions Please consider building the synchronization between the Incidents on JSM and Opsgenie. h3. Current Workarounds # Complete the JSM Cloud integration. # Set up the Incident Rules on the associated teams to match the JSM issues that are created in the "Incident" Issue Type. In this way, whenever a JSM Incident is created, an Opsgenie Alert and an Opsgenie Incident will be generated automatically. |
New:
h3. User Problem
In the current design, the JSM integration is only for Opsgenie Alerts and JSM issues syncing. However, the term, Incident, exists on both products for the similar objective, it makes more sense to have the synchronization between them. h3. Suggested Solutions Please consider building the synchronization between the Incidents on JSM and Opsgenie. h3. Current Workarounds h4. For JSM to Opsgenie # Complete the JSM Cloud integration. # Set up the Incident Rules on the associated teams to match the JSM issues that are created in the "Incident" Issue Type. In this way, whenever a JSM Incident is created, an Opsgenie Alert and an Opsgenie Incident will be generated automatically. h4. For Opsgenie to JSM # Configure the Action Filter on the JSM Cloud integration to only post the Responder Alerts, which are created by the Opsgenie Incident for the associated teams, to create an JSM issue in the "Incident" Issue Type. In this way, whenever an Opsgenie Incident is created, Opsgenie will create the Responder Alert to the team who is listed as a Responder Team, and Opsgenie will post this alert data to create a JSM Incident accordingly. |