Unavailable fields in Alerts API when migrating from OpsGenie

David Johnson
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 2, 2024

We are in the process of migrating our internal tools from OpsGenie to JSM.

The JSM Alerts API is almost identical to that of OpsGenie but there are some key differences which are currently blocking our transition.

1. "Get Alert" [`GET /v1/alerts/{id}`] does not include a `report` field which previously contained `ackTime`/`closeTime`/`acknowledgedBy`/`closedBy`.

I cannot see where these details can now be pull from.

2. "Acknowledge Alert" [`POST /v1/alerts/{id}/acknowledge`] and many other endpoints used to accept a `user` field in the request body which attributed the action to that user.

Is this no longer possible? We currently use a service account which performs actions for the user who is authenticated by an internal provider.

0 answers

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events