Start building your teams, integrate your tools and create on-call schedules.
Start building your teams, integrate your tools and create on-call schedules.
Learn how to configure your profile, get notifications from Opsgenie and view on-call schedules.
Advanced Opsgenie account settings and other reference information
Learn how to receive and manage alerts, create policies and encrypt alert data.
Learn all the ways to create an integration, use Opsgenie's integration framework and check system health with Heartbeats.
Notify the right users, investigate potential causes and take preventive actions to avoid future incidents.
Manage your services, create service relationships, view the service status and report problems.
Learn all the ways to set up Opsgenie actions, create channels and execute actions.
Learn how to use Opsgenie's integration server to connect your internal and external systems.
Analyze Opsgenie activity with global and team reports.
Learn all the ways to log in Opsgenie, set password policies and administer user accounts.
What does Opsgenie offer Jira Service Management users?
Opsgenie provides a powerful two-way integration with Jira Service Management. When a new issue is created in Jira Service Management, a corresponding Opsgenie alert is automatically created, containing rich information about the issue. Opsgenie provides rich notifications with on-call rotations, scheduling features, and alert escalations to ensure the best alert and incident management for Jira Service Management customers. As users execute actions on the alerts, like acknowledge or snooze, the issue in Jira Service Management automatically updates with comments about these alert actions. If users close the alert, the issue in Jira Service Management is resolved (Only if the issue has a Resolve the issue transition).
Functionality of the integration
Jira Service Management to Opsgenie:
When an issue is created in Jira Service Management, an alert is created in Opsgenie.
When a comment is added to issue in Jira Service Management, the same comment is added as a note to the alert in Opsgenie.
When an issue is closed and resolved in Jira Service Management, the alert in Opsgenie is closed.
Opsgenie to Jira Service Management:
If Send Alert Updates Back to Jira Service Management is enabled, actions for Jira Service Management are executed in Jira Service Management when the chosen action is executed in Opsgenie for alerts which are created by the Jira Service Management integration.
If Create Jira Service Management Issues for Opsgenie Alerts is enabled, actions for Jira Service Management are executed in Jira Service Management when the chosen action is executed in Opsgenie for alerts which have a source other than the Jira Service Management integration.
This action mapping features are explained in detail in the Action Mapping Feature section below.
Adding Jira Service Management Integration in Opsgenie
From your Opsgenie account, go to Integrations and select Jira Service Management Integration
Specify who is notified of Jira Service Management alerts using the Teams field. Auto-complete suggestions are provided as you type.
Copy the integration URL to use in the Jira Service Management configuration.
Click Save Integration.
If you are using SSO to login to Jira, you need to generate an API token and use this token as the password in the integration settings password field. View these instructions to generate an API token in Jira.
After generating your new token, copy and paste it to the password field of the Jira Service Management integration in Opsgenie. Save the integration.
Users who don't have Atlassian Account
Users who are authenticating against the REST API but do not have Atlassian Accounts, need to convert them to Atlassian Account. You can check here to see the instructions to convert Atlassian Account.
Action Mapping Feature
Opsgenie allows customers to define action mappings between Opsgenie actions and Jira Service Management actions.
To use the Action Mappings feature, provide some information to the integration which are listed below:
Issue Type Name: The issue types defined in Jira Service Management e.g. Task, IT Help, Sub-task, Service Request or any other custom defined type. Make sure you write the issue type syntax error-free.
Jira Service Management URL: This is the domain name of your service e.g. https://testops.atlassian.net
Username: The e-mail address you use to login to Jira Service Management.
Password/API Token: The password or API token you use to login to Jira Service Management.
Project Key: The key of the project you want to create alerts from e.g. OT, OPS, SIT. The project key is usually in capital letters so make sure you write it in the right form.
For alerts created by Jira Service Management
You can use this section to map Opsgenie actions to Jira Service Management actions when the source of the alert is Jira Service Management (i.e When the alert is created by Jira Service Management integration.)
You can map different Opsgenie actions to different Jira Service Management actions. For example, you can add note to Jira Service Management issue, when the alert is acknowledged. In order to do this, you should define If alert is acknowledged in Opsgenie, add it as a comment to the issue in Jira Service Management. mapping in Send Alert Updates Back to Jira Service Management section.
For other Opsgenie alerts
You can use this section to map Opsgenie actions to Jira Service Management actions when the source of the alert is NOT Jira Service Management (i.e When the alert is created by another integration.)
For this purpose, you can use Create Jira Service Management Issues for Opsgenie Alerts section. In order to use this functionality, you need to map one Opsgenie action to create an issue Jira Service Management action. The Opsgenie action doesn't have to be alert is created, it can be other actions as well.
a tag is added to the alert and a custom action is executed on alert actions differ from other actions. When one of these actions is selected, an extra field is added to enter for which tags or for which custom action this mapping works.
Enter multiple tags by separating the tags with a comma. If multiple tags are entered, the mapping works if the alert has one or more of the specified tags. For the mapping to work for any tag, leave the tags field empty.
If an Opsgenie action is mapped to multiple Jira Service Management actions, an error occurs except for the a tag is added to the alert and a custom action is executed on alert actions. Save multiple mappings for these actions because they differ by the given tags and the given custom action names.
Configuration in Jira Service Management
Log in to Jira as an administrator.
From the dashboard, open the Administration menu. Select System.
From the left, select Webhooks under "Advanced".
4. Click Create A Webhook. In the opening section, paste the URL provided by Opsgenie's Jira integration into URL input. Click Create.
Now manage your Jira Service Management alerts at Opsgenie and leverage its full alerting functionality.
Sample payload sent from Jira Service Management
Create Alert payload:
Integration via OEC (for On Premise Jira Service Management Usage)
Jira Service Desk is now Jira Service Management! The product name may have changed, but we'll continue using the old name (Jira Service Desk) in the scripts until the next update.
Use Opsgenie's OEC and the Jira ServiceDesk script to update requests on Jira Service Management. This enables the deployment of your own scripts/ability to modify the ones provided and execute customized actions on Jira Service Management.
To use the Jira ServiceDesk integration package, follow the steps in the sections below through the end.
Download the latest version of OEC
To download the latest version of JiraServiceDesk package, please use readme file of oec-scripts repository.
For Red Hat Based Distributions
Run following command : rpm -i opsgenie-jiraservicedesk-<your_version>.rpm
For Debian Based Distributions
Run following command : dpkg -i opsgenie-jiraservicedesk-<your_version>.deb
Unzip opsgenie jiraservicedesk zip file which contains OEC package into a directory (C:\opsgenie is the preferred path.) Follow the instructions here to install OEC on Windows.
In order to learn more about how to run OEC you can refer to the Running OEC documentation.
Configuring Jira Service Management Integration for OEC
In order to use OEC utility, enable Send Via OEC.
Other configurations regarding Jira Service Management can be done either via integration page or OEC configuration file config.json. The configuration via the integration page precedes the configuration file.
To be able to execute actions in Jira Software, OEC gets the configuration parameters from the configuration file located at path /home/opsgenie/oec/conf/config.json.
apiKey – Copy the API key from the Jira integration you've created above.
issueTypeName – Type of the issue which can be "Task", "Bug", "Story" or your custom issue type ("Epic" is not supported).
url – Your Jira Service Management url where issues will be created, resolved, closed etc.
username – Your username for your Jira Service Management account.
password – Your password for your Jira Service Management account.
key – The issues will be created for this project.
The package that you downloaded also includes OEC utility which is located under /usr/local/bin and the script that is needed to be run by OEC which is under /home/opsgenie/oec/scripts. After the configuration of OEC is done, you need to run it. In order to learn more about how to run OEC, you can refer to the Running OEC documentation.
Sample parameters sent to OEC
If a mandatory custom field is set for creating an issue in Jira Service Management, a Jira Service Management issue cannot be created from an Opsgenie alert. However, by using OEC and configuring the script, the creation of Jira request can be achieved.
If a comment cannot be added to an issue by performing an action on an alert, please look at the Logs page first. If the URL does not contain the issue key it means there is no issue in Jira ServiceManagement populated from that alert. Thus it could not add a comment to a non-existing issue.
Opsgenie's Jira Service Management Integration allows setting the status of the issue to RESOLVED in Jira Service Management. However, if the workflow of the project does not allow that transitions, you cannot set that transition using Opsgenie too.
Jira Service Management does not support non-ASCII characters. Having non-ASCII characters on payload to be sent to Jira Service Management may cause 400 Bad Request Error.
If the Jira Service Management integration is assigned to a team, in order to create issues in Jira Service Management from alerts created in Opsgenie, the other integrations must also be assigned to the same team, or, no team must be assigned for both the Jira Service Management integration and the other Opsgenie integrations.
Was this helpful?