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
4,359,848
Community Members
 
Community Events
168
Community Groups

Add impacted service to an incident using the API

Edited

Hello,

There is a use case where it is possible to add impacted services through the UI but not from the API (https://docs.opsgenie.com/docs/incident-api), this is something that would help automate the grouping and the general handling of incidents.

Is it possible to do it automatically apart from Incident rules?

Are any plans to add this in the future?

Thank you!

1 answer

1 accepted

2 votes
Answer accepted
Nick H Atlassian Team Jun 03, 2021

Hi @Javier Diaz Martin ,

It's unfortunately not possible to add / update the impacted services via the API, but we have an open feature request for this I've added you to. That ticket for reference is OGS-1821; Incident API - Availability for updating impactedServices.

Since our tickets are not public, we'll reach out directly if/when there are any updates on this. As for a workaround - which I'm aware is not really the best - you could use the Add Responder API to add those who would be impacted by the incident: https://docs.opsgenie.com/docs/incident-api#add-responder-to-incident

Nick H Atlassian Team Jun 03, 2021

Otherwise - the impacted service(s) would need to updated manually within the Opsgenie app.

Thank you, Nick.

I'm looking forward to this change, another great addition to the Incident API is to be able to associate alerts.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
TAGS
Community showcase
Published in Jira

Online AMA this week: Your project management questions answered by Jira Design Lead James Rotanson

We know that great teams require amazing project management chops. It's no surprise that great teams who use Jira have strong project managers, effective workflows, and secrets that bring planning ...

172 views 1 6
Read article

Atlassian Community Events