Setting Priority Level for Integrations

[Henry Painter]

I understand there are some limitations where some integrations are assigned a default (P3) priority if OpsGenie cannot determine the priority from the payload.

https://support.atlassian.com/opsgenie/docs/what-is-the-priority-level-of-integration/

I have been relying upon this override, and attached screenshot of the API integration in question, and its settings.

 

Despite this the alerts are still being treated as P3.  It appears this functionality is not working.

Am I doing something wrong?

[Nick H]

Hi @Henry Painter ,

Engineering is aware of this issue currently. It's a minor Bug you can watch, follow and vote or here: https://jira.atlassian.com/browse/OPSGENIE-1188

[Ajay _view26_]

Hi @Henry Painter 

Welcome to the Atlassian Community 

The API does provide a setting to set the Priority in the body. Have you tried it out?

POST https://api.opsgenie.com/v2/alerts

{

"message": "Forge App Incident from Atlassian",

"description": "Your app XYZ is now in an alert state",

"responders": [

{

"id": "4513b7ea-3b91-438f-b7e4-e3e54af9147c",

"type": "team"

}

],

"tags": [

"Automation",

"Critical"

],

"details": {

"key1": "value1",

"key2": "value2"

},

"entity": "An example entity",

"priority": "P1"

}