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.