Opsgenie alert rule does not seem to be working

[Haseeb Khan]

I have a Jira-> Opsgenie integration that I'm trying to get matched for priority. In Jira there is P0-P3 and in Opsgenie there's P1-P5. When I have an P0 in Jira, it defaults to P3 in opsgenie as it does not recognize P0. This is messing with our alerting. I'm trying to add filtering to help resolve this with the end goal being the following in priority of ticket/alert in Jira and Opsgenie respectively: P0->P1 ; P1->P1 ; P2->P2 ; P3->P3. When I set up an action with priority to be matching, it works fine for P1,P2,P3 Jira tickets but fails for P0 for the above reason. I am trying to set up an alert rule that can catch this P0 ticket to assign it to a P1 manually but it is failing. As you can see, This ticket was put in as a P0 ticket and it is missed by the "alert on P0" rule. Any input is appreciated.

[Connor]

Hi @Haseeb Khan to see why that alert rule is not working as you expect, you should look through the JSM ops audit log to see what information JSM is receiving when the alert is created. My guess is your "Priority NOT Equals P0" condition is not being evaluated correctly because the priority value in the webhook data doesn't exactly match P0.

You might not need to use this workaround though. Within your JSM project settings you can map issue priorities to alert priorities. i.e. map issue priority P0 to alert priority P1. The only caveat is that might only be for incident issues, so if you need this for other issue types you'll have to do some testing to verify if it will work. Here's the documentation that describes how to do this priority mapping. For convenience here's the exact steps:

From your service project, select Project settings, then Operations, then Incident management. Then select Assign alert priorities.