JIRA
  • 25 Apr 2023
  • 5 Minutes to read
  • Dark
    Light
  • PDF

JIRA

  • Dark
    Light
  • PDF

Article Summary

JIRA Integration Guide

JIRA is a project management tool that enables collaboration between teams within an organization. Integrate AlertOps’ alert management platform with JIRA to receive and respond to critical alerts through email, SMS, push notification, and phone alerts. AlertOps ensures that alerts received from JIRA always reach the correct, available team member by utilizing escalation policies and on-call schedules.

Inbound Integration

AlertOps Configuration

  1. From the main menu, click on Configuration and select Integrations from the sub menu.
  2. In the Inbound Integration section, select API from the integration type dropdown menu.
  3. Click the 'ADD API' button.
  4. You will be redirected to a list of API integration templates. Select JIRA from the list.
  5. To set up the integration, enter a name for the integration. Select an Escalation Policy to guide escalations coming from this Integration. And enter the names of recipient group(s) and recipient user(s).
  6. Click the Submit button to save this integration.  Graphical user interface, text, application, email  Description automatically generated
  7. Once saved, click 'COPY URL' to copy the URL endpoint to be used in the JIRA configuration.

Advanced Settings

The final configuration we need to make to this integration is to add JIRA values to open, close, or update an alert.

  1. Expand Rules for Opening and Closing an alert in the advanced settings of this integration.
  2. Issues coming from JIRA have a SourceStatus that corresponds to transition titles. This means we need to add transition titles as additional values in the alert rules.  These are client-environment specific, so you need to customize these accordingly. Note that these values are case sensitive and must match the JIRA transition names exactly. In our example we will add the generic To Do and Done JIRA labels:
  3. Click the green checkmark to save these changes.

JIRA Configuration

  1. Create a Webhook to send Issues to AlertOpsGraphical user interface, text, application, email  Description automatically generated

    Graphical user interface, application, Teams  Description automatically generated

  2. Paste the URL endpoint from the Integration we created in AlertOps and select the Issues that will create alerts in AlertOps.

Issues coming from JIRA will now produce alerts.


JIRA Outbound

Add Custom Fields

In AlertOps, a Template is used to create custom attributes.  In most cases, where only a small number of Attributes are created, extending the Standard Template is sufficient, though you can create a new one if you choose.  

Create the following custom Attributes:

A picture containing table  Description automatically generated

Outbound Integration Configuration

To create the Outbound Integration:

  1. Click Configuration on the main menu and select Integrations menu.
  2. In the Outbound Integrations section, click the Add Outbound button.
  3. Set the Integration Name as JIRA.
  4. Set the Web Security Type as Basic.
  5. Set the Username as your JIRA username.
  6. For the Password, enter the API Token for your JIRA account.
  7. Press Submit to save this Outbound Integration.Graphical user interface, application, Teams  Description automatically generated


Create Methods

Once the integration has been saved, we can now create Methods to make changes in JIRA.

To add a Method to an Outbound Integration, click the Add Method button on the right.

Below we will configure three different Methods: Create Issue, Transition Issue, and Add Issue Comment.

Create Issue 

A picture containing text, screenshot, indoor  Description automatically generated


//URI
//https://YourJiraEnvironment.atlassian.net/rest/api/2/issue

//Request Data
{"fields":{"project":{"key":"YourProjectKey"},"summary":" <<Alert.Topic>>","description":"<<Message.MessageText>>","issuetype":{"name":"Task"}}}

//Response Data
{"id":"<<Attribute.JIRAIssueID>>","key":"<<Attribute.JIRAIssueKey>>","self":"https://YourJiraEnvironment.atlassian.net/rest/api/2/issue/10007"}

Close (Transition) Issue

First we need to input the Issue Key field in the URI that we mapped in our inbound integration to identify the issue to be updated.

In order to close an issue in JIRA, we need to identify the Transition ID that corresponds to whatever status is used as the closed issue state in your environment. These are client-environment specific, so you need to identify and customize these accordingly.

In this example, a closed state is 'Done' with a Transition ID of 21 so we would input that into the request data.  

Graphical user interface, application  Description automatically generated

//URI
//https://YourJiraEnvironment.atlassian.net/rest/api/2/issue/<<Attribute.JIRAIssueKey>>/transitions

//Request Data
{"transition":{"id":"31"}}

Add Issue Comment (Optional)

In this example we will be adding a comment to an issue when a user is assigned. This comment can be customized to use any available fields to suit your needs. In our example, we will be commenting the username of the assignee. 

First we need to input the Issue Key field in the URI that we mapped in our inbound integration to identify the issue to be updated.

The next step is to add the assignee to the comment. We can drag and drop this field from the list of available fields on the left.

Graphical user interface, application  Description automatically generated

//URI
//https://YourJiraEnvironment.atlassian.net/rest/api/2/issue/<<Attribute.JIRAIssueKey>>/comment

//Request Data
{"body":"Issue was Assigned to <<Alert.OwnerUserName>>"}

Workflow Configuration

Now that we have configured our Methods, we need to create Workflows to trigger the Outbound Integration. 

  1. Click Configurations from the main menu and select Workflows.
  2. Click the Add Workflow button.  

Below we will create three Workflows with Actions to trigger the methods we have just created: 

Create Issue Workflow

  1. For Type, select Alert.
  2. Name the workflow JIRA - Create Issue
  3. Set the Alert Type as a Standard Alert
  4. Click Submit to save. 

Once saved we can add Start Conditions to this Workflow:

  1. Using Match All Conditions.
  2. Add AlertStatus is Open. 
  3. Check the green arrow to save.

Next, we need to add an Actions to this Workflow. Click the Add Action Button.

From here we are going to select Outbound Service Notification for the Action, and select the corresponding Method we want to trigger as the Web Method. 

Once this has been saved, make sure to enable the Workflow before continuing. 


Close (Transition) Issue Workflow

  1. For Type select Alert
  2. Name this Workflow JIRA - Transition Issue 
  3. Select Standard Alert for the Alert Type
  4. Click Submit to Save.

Once saved we can add Start Conditions to this Workflow:

  1. Using Match All Conditions.
  2. Add AlertStatus is Closed. 
  3. Check the green arrow to save.

A screenshot of a computer  Description automatically generated

Next, we need to add an Actions to this Workflow. Click the Add Action Button.

From here we are going to select Outbound Service Notification for the Action, and select the corresponding Method we want to trigger as the Web Method.

Once this has been saved, make sure to enable the Workflow before continuing.

Add Comment on Assignment Workflow (optional)

You can add comments to a JIRA Issue. In this example we will add a comment when an an alert is assigned. 

  1. For Type select Alert
  2. Name this Workflow JIRA - Add Note on Assignment
  3. Select Standard for the Alert Type.
  4. Click Submit to save.

Once saved we can add Start Conditions to this Workflow:

  1. Using Match All Conditions.
  2. Add AlertStatus is Assigned. 
  3. Check the green arrow to save.

Next, we need to add an Actions to this Workflow. Click the Add Action Button.

From here we are going to select Outbound Service Notification for the Action, and select the corresponding Method we want to trigger as the Web Method.

Once this has been saved, make sure to enable the Workflow before continuing.

Using Workflows in Escalation Policies

The next step for workflows is to associate them with an Escalation Policy from the Automation tab. 



Was this article helpful?

What's Next