nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Cannot match P5 information from OpsGenie with Lowest from JIRA

Marlon Silva_v5nopp

We cannot seem to find a way to match the priority of the alert in OPSGENIE from JIRA. there is no issue with P1-P4 between OpsGenie and Jira. But when I created a JIRA ticket with Lowest as priority, when it creates an alert in OpsGenie it still shows as P4. I already set it to create as P5-Information in OpsGenie but still shows as P4. Please see screenshot below for my current setting. I also included the test ticket i created and it shows that it is Lowest Priority ticket. Is there something that I missed? but it worked on the other priority. Please advice. Thank you

OpsGenie P5.JPG OpsGenie P5 activity log.JPG Jira P5.JPG

Accepted answers

Nick Haller

Hi @Marlon Silva ,

Is your P4 create alert action mapping to the Priority Contains "Low" by chance?

If yes - then my guess is the P5s (Lowest) are matching on that condition - since it would contain "Low." And if that's the case, then you may want to change the P4 create alert action mapping to the Priority Equals "Low."

That might not be the case - with the JSM Priority being "Low" but seems like it could be. Regardless, seems like the "Lowest" alerts are matching on the P4 create alert action and its conditions so that might give an idea of what could be happening.

All comments

Nick Haller

Hi @Marlon Silva ,

Is your P4 create alert action mapping to the Priority Contains "Low" by chance?

Marlon Silva_v5nopp

I set on the P5 create alert action to map with Lowest in JSM as shown on the screenshot. the ticket I created a ticket in JSM with lowest priority but still shows as P4 in OpsGenie upon checking in the Alerts tab.

Nick Haller

Right, but the P5s / Lowest JSM issues are matching on this create alert action:

For context, these actions are processed top >> down in an order of operations. Opsgenie will review the top action, and if Opsgenie does not match the action's filter/conditions, look at the next action(s) until a match is made.

So it seems like the Lowest JSM issues are matching on this action before actually reaching the Lowest Opsgenie create alert action.

Again - if your Low create alert action is parsing on the Priority Contains Low - then that'd be the issue - since "Low" is contained in "Lowest."

Marlon Silva_v5nopp

is there a way to correct this?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

opsgenie