OpsGenie>Jira - Set priority of created tickets

[Mark Skrzypczyk]

I've been looking over the documentation for this integration (Jira Software Cloud) and the various settings in the integration in OpsGenie but can't see one that allows for setting the priority of any tickets that are first create in OpsGenie and sent to Jira.

This is a new setup and we've decided to only push P2 or higher alerts over to Jira and I have that bit setup, however, they are showing at Medium (P3) in Jira.

Whilst there is a trigger for "If Priority is updated" there isn't an action to perform in Jira to edit it on that side, with the only meaningful option being to add a comment which obviously isn't ideal.

[Gunsa]

-

[Nick H]

Hi @Mark Skrzypczyk !

Thanks for reaching out. At this time Opsgenie > JSD does not have this functionality out-of-the-box. We do have an open feature request that I can certainly add you to though. In the meantime - the workaround requires a few steps in both Opsgenie and JSD.

In Opsgenie - you will want to create an Alert Policy (under the Settings tab > Global Policies) that adds the priority to the alert's message or description field. Alert policies are used to modify alerts upon creation: https://docs.opsgenie.com/docs/global-policies#alert-policy

The setup might look something like this:

Then in JSD you will want to add automation rules that filter on the priority that is now being sent in the ticket's Summary or Description. Similar to OG's Alert policies, Automation rules can be used to used to modify tickets upon creation (along with other actions): https://support.atlassian.com/jira-service-desk-cloud/docs/set-up-rules-to-automate-repetitive-tasks/

These can be added under Settings > System > Automation Rules. One of the rules might look something like this:

My rule above looks for "P1" in the Summary of the ticket and maps these to Critical priorities in JSD. Here is a test example as well:

Hope this helps! Please let us know if you have any followup questions.

Best,

Nick

[Gunsa]

I am having the same issue, is there any way to sync the priority fields with out automation? has this been resolved? 

[Nick H]

Hi @Mark Skrzypczyk , @Gunsa , and others,

We'll be releasing a new Jira/JSM integration framework soon that has the ability to map Opsgenie alert priority to Jira/JSM issue priority. Automation rules won't be needed like I mentioned above last year.

Having said that, the new integration framework is currently in Early Access, so to join the program, you'd have to enter a ticket with Opsgenie support here: https://support.atlassian.com/opsgenie/

Our team can get this enabled in your account. For more information about the framework as well, check out the new documentation: https://support.atlassian.com/opsgenie/docs/integrate-opsgenie-with-jira-software-cloud/

Let me know if you have any other questions.

[Andrew Bozanich]

Hi @Nick H

I have created an Opsgenie integration with the newly released Jira integration with the hope of taking my alerts coming from 3rd party montioring systems, and creating a Jira software cloud ticket. I have gone through the steps to configure the custom fields on the integration and have selected it to create a P2 jira ticket. However when the Jira ticket is created it is always created as the default P3. I have tried this on multiple projects and have reviewed the data package being sent from OG to jira and found that it has the correct data there however Jira seems to ignore the selection/data being provided. Is there something on the jira side that needs to be checked or changed to see if its blocking that info from coming in? It is placing the other detail in the ticket, as an example we have a custom field for team selection and the team is selected when the ticket is created. It is only the priority field that is getting dropped. 

Thanks for the help!

Andrew

[Nick H]

Hi @Andrew Bozanich ,

Do you have an outgoing action that maps certain types of alerts and their priority to Jira issues and the priority of those when opened?

Below is an example of how I've been able to map P1 Opsgenie alerts to Blocker Jira issues: