Rootly Integrations

⌘K
Back
Overview
Slack
Installation
Workflows
Commands
Mattermost
Installation
PagerDuty
Installation
Workflows
Alerts
Opsgenie
VictorOps (Splunk On-Call)
Jira
Jira (On-Premise)
Confluence
Confluence (On-Premise)
Service Now
Installation
Workflows
Google Docs
Statuspage.io
Importing Status Pages
Importing Templates
Creating a StatusPage Incident
Using Status Page Templates
Dropbox Paper
Notion
Quip
Grafana
Looker
New Relic
Installation
Alerts
Datadog
Installation
Alerts
Kubernetes
Honeycomb
Heroku
AWS Elastic Beanstalk
Gitlab
GitHub
Google Meet
Zoom
Webex
GoToMeeting
Microsoft Teams
Zendesk
Linear
Installation
Workflows
Shortcut
Airtable
Trello
Installation
Workflows
Asana
Installation
Workflows
Freshdesk
Installation
Workflows
Nobl9
Backstage
Installation
Twitter
Email
SMTP
SendGrid
Sentry
Rollbar
Prometheus
Zapier
API
Terraform
Pulumi
HashiCorp Vault
SSO
SCIM
Docs powered by archbee 

Jira

18min

Why

Jira Integration allows you to:

  • Creating an incident in Rootly will create an issue in Jira if you choose to.
  • Creating an action item in Rootly will create an issue in Jira if you choose to. Attached as subtasks if incident has been created in Jira as well.
  • Changing incident title, description, status in Rootly will update the issue in Jira.
  • Changing action item title, description, status in Rootly will update the issue in Jira.
  • Changing Jira incident issue attributes will not update incident attributes in Rootly.
  • Changing Jira action item issue attributes will update action item attributes in Rootly. ( See Webhooks section to make this feature works )

Installation

You can setup this integration as a logged in admin user in the integrations page:

Document image


We recommend you integrating with a service account to make sure the integration doesn't break if a user leaves your company.

Settings

You custom map your Jira issue status to Rootly ones through the Integration Settings page.

Document image


Custom fields mapping

You can configure custom column mapping using our custom variables Incident Variables.

How to find id for custom field(s)?

https://confluence.atlassian.com/jirakb/how-to-find-id-for-custom-field-s-744522503.html

JSON
|
{
  "customfield_10029": "{{incident.severity}}",
  "customfield_10030": "{{incident.started_at | date: '%FT%T%:z' }}"
  // For Rootly multi select to Jira textfield
  "customfield_10031": "{{incident.custom_fields | find: 'custom_field.slug', 'your-slug' | get: 'selected_options' | map: 'value' }}"
  // For Rootly select/multi select to Jira simple select
  "customfield_10038": { "value": "{{ incident.raw_groups | first | get: 'name' }}" }
  // For Rootly multi select to Jira multi select
  "customfield_10032": {{incident.custom_fields | find: 'custom_field.slug', 'command-pilot-unit' | get: 'selected_options' | to_values }}
   // For Rootly multi select to Jira labels
  "customfield_10033": {{incident.custom_fields | find: 'custom_field.slug', 'command-pilot-unit' | get: 'selected_options' | map: 'value' | to_json }}
   // For Rootly number field to Jira number field
  "customfield_26117": {{ incident.custom_fields | find: 'custom_field.slug', 'command-pilot-unit' | get: 'selected_options.value' }}
  // For Rootly datetime field to Jira datetime field
  "customfield_26218": "{{ incident.custom_fields | find: 'custom_field.slug', 'incident-contained-time' | get: 'selected_options.value' | date: '%Y-%m-%dT%H:%M:%S.%d%z' }}"
}


Update payload add issuelinks example

JSON
|
{
   "issuelinks": [
      {
         "add": {
            "type": {
               "name":"Action",
               "outward":"action item for"
            },
            "outwardIssue": {
               "id":"{{ incident.jira_issue_id}}"
            }
         }
      }
   ]
}


Update payload add comments example

JSON
|
{
    "comment":[
        {
            "add": {
                "body":"Bug has been fixed."
            }
        }
    ]
}


Update payload severities example

JSON
|
{% if incident.severity_slug == 'sev0' %}
  { "priority": [ { "set": { "name" : "High" } } ] }
{% elsif incident.severity_slug == 'sev1' %}
  { "priority": [ { "set": { "name" : "Medium" } } ] }
{% elsif incident.severity_slug == 'sev2' %}
  { "priority": [ { "set": { "name" : "Low" } } ] }
{% endif %}


Oauth Permissions

Your selected workspace needs the following oauth permissions:

  • read:application-role:jira
  • read:avatar:jira
  • read:field-configuration:jira
  • read:group:jira
  • read:issue:jira
  • read:issue-status:jira
  • read:issue-meta:jira
  • read:issue-security-level:jira
  • read:issue-type:jira
  • read:issue-type-hierarchy:jira
  • read:issue.changelog:jira
  • read:issue.transition:jira
  • read:issue.vote:jira
  • read:priority:jira
  • read:project:jira
  • read:project-category:jira
  • read:project-version:jira
  • read:project.component:jira
  • read:project.property:jira
  • read:status:jira
  • read:user:jira
  • read:user.property:jira
  • write:attachment:jira
  • write:comment:jira
  • write:comment.property:jira
  • write:issue:jira
  • write:issue.property:jira

Permissions

Your selected workspace needs the following permissions:

  • Assign Issues - Ability to assign issues to other people
  • Close Issues - Ability to close issues. Often useful where your developers resolve issues, and a QA department closes them.
  • Create Issues - Ability to create issues.
  • Delete Issues - Ability to delete issues.
  • Edit Issues - Ability to edit issues.
  • Link Issues - Ability to link issues together and create linked issues.
  • Transition issues - Permission to transition (change) the status of an issue.

More help on https://confluence.atlassian.com/adminjiraserver073/managing-project-permissions-861253293.html

Webhooks

To get Jira to update Rootly action items, you need to configure Webhooks. Additional documentation can be found here.

Go into Jira Software System panel > Webhooks

Document image




Create a new webhook and copy the Rootly webhook url into the url input.

Document image




Finally let's allow the webhook to listen to Issue events.

Document image




All done !

Create Incidents from Jira Tickets Automatically



Support

If you need help or more information about this integration, please contact support@rootly.com or use the lower right chat widget to get connected with an engineer.

Uninstall

You can uninstall this integration in the integrations panel by clicking Configure > Delete

Updated 04 May 2023
Did this page help you?
Yes
No
PREVIOUS
VictorOps (Splunk On-Call)
NEXT
Jira (On-Premise)
Docs powered by archbee 
TABLE OF CONTENTS
Why
Installation
Settings
Custom fields mapping
Update payload add issuelinks example
Update payload add comments example
Update payload severities example
Oauth Permissions
Permissions
Webhooks
Create Incidents from Jira Tickets Automatically
Support
Uninstall