The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Associate issue priority with escalation policies

Carlos Sanchez
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!
August 18, 2021

Hi there guys

I'd like to know if there's a way to associate the priority of an issue raised on Jira

and based on that notify teams on opsgenie using escalation policies.

I noticed opsgenie escalation policies allow to send notification based on the alert

generated only and not the issue priority.

 

thanks in advance guys.

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

0 votes
Nick Haller
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
April 6, 2022

Hi @Carlos Sanchez ,

That's correct - "escalation policies allow to send notification based on the alert generated only and not the issue priority."

But routing rules can filter on the alert's priority, or the priority being sent from Jira (as long as it's being parsed in an Opsgenie alert field), and send each specific alert to a certain escalation path:

rr11.jpg

 

With the configuration above, P1 and P2 alerts would be routed to a Critical escalation policy, which takes a more aggressive path of notifying users. While all other alerts would be routed to the other escalation, which takes a more relaxed path since these might be considered more informational.

TAGS
AUG Leaders

Atlassian Community Events