Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

OpsGenie --> JSM Inegration (control fields that are passed)


I have the following questions about the OpsGenie to JSM integration: 

  1. How do I control the fields that OpsGenie will pass to JSM. At present, all that is passed is the summary.
    1. I understand that custom fields cannot be mapped (without OEC), however, there must be a way to include more data in the JSM ticket? Impacted Service for instance
  2. I have noticed that some of the issues created by OpsGenie in JSM are created with a request type, whilst others are not. Furthermore, the Ones without a request type contain the label 'FromOG', the ones with a request type do not
  3. How can I search in JQL (or another route) for alerts that are created via OpsGenie? This is so I can look at automation rules to update other issue fields with OpsGenie alert content but only where the issue is raised by OpsGenie 


On a separate note, how do I associate an alert with a Service? We are looking at OpsGenie as a centralised event management alerting tool but without the ability to see which services link to which alerts it's falling short.



Dave W 


1 answer

0 votes
Nick H Atlassian Team Apr 20, 2021

Hi @David Wimbush 

Thanks for reaching out. I'll try to address those with the same bulleted numbers;

1) At this time only the Opsgenie alert's Message maps to the JSM issue's Summary, and the alert's Description maps to the issue's Description.

Like you mentioned, OEC can be used to map Opsgenie alert fields to JSM issue fields - regardless if they are custom or not. We just typically see OEC being used more frequently for required custom fields. 

We do have a new Jira / JSM framework being released that will be able to map Opsgenie alert fields >> JSM issue fields out-of-the-box without OEC. I don't have an ETA just yet on when that'll be, but we'll keep you updated when that is pushed! 


2) If a Jira issue is created from an Opsgenie alert through an outgoing Jira integration, the label 'FromOG' will appear on the issue:



While alerts that create issues through linking will not show the 'FromOG' label:



3) I would suggest using the JQL labels = fromOG to search for issues created by Opsgenie. Again - this will pull any with that label that were created through the Jira integration(s):



Hope this helps. Let us know if you have any additional questions, issues, etc.

Hi Nick,

First off, thank you for the prompt and thorough response! 

Okay, understood. Do you have a ballpark ETA on the OpsGenie --> JSM expansion that will allow for custom/additional field mapping? If we're talking a month or so, I will wait. However, if we're looking at 2-3 Months+ I will look at an OEC integration for the time being. 

Regarding Point 2) I have seen issue in my linked JSM project that have been generated by OpsGenie but do not include the label 'From OG' (See attached).




Is there something else I'm missing here? I've compared the logs and alert detail from the ones with and without the labels and as far as I can tell, there is no difference in configuration. 

On a seperate topic, I can't seem to get OpsGenie to create incidents from Alerts. I've configured this within the Service Rules (I tried matching alert content on a number of fields), however, no Incidents are created.


Service Rules:

Untitled 2.png

When an alert comes through, that references 'Service Name 1', no Incident is created. Any ideas why this might be the case? 


Dave W 

Nick H Atlassian Team May 03, 2021

Hi @David Wimbush ,

Sorry for the delay. I believe the new framework beta will be rolled out over the next week or so. We should be announcing this in-app, so be on the lookout for that. 

AFAIK - any Opsgenie alert that creates a Jira/JSM issue through the integration will add the FromOG label. So I'm wondering if you are creating issues through another method? Or if you have some automation rule(s) configured in Jira/JSM that are stripping the label.


As for the Incident Rules query - those conditions need to match one or more of the alert fields AFTER it's created / the data parses into those fields. So you would have to have "Service Name 1" included in one of these alert fields for one of those conditions to match:


If the alert is matching on one of those conditions, it could be associating with an open existing incident as well:

If it's associated with the incident, there should be an option to click into the incident, or check if it's associated:


Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira

Online AMA this week: Your project management questions answered by Jira Design Lead James Rotanson

We know that great teams require amazing project management chops. It's no surprise that great teams who use Jira have strong project managers, effective workflows, and secrets that bring planning ...

172 views 1 6
Read article

Atlassian Community Events