Skip to main content

​
Introduction

The Jira On-Premise integration connects Rootly with your self-hosted Jira Data Center instance. It supports the same workflow actions as Jira Cloud — creating issues, subtasks, and syncing status — but authenticates directly against your instance URL rather than through OAuth. You can connect with username + password (Basic Auth) or a Personal Access Token (PAT). Multiple instances are supported, allowing you to connect more than one Jira Data Center environment to a single Rootly organization.

​
Before You Begin

Before setting up the integration, make sure you have:
  • A Rootly account with admin permission to manage integrations
  • Your Jira Data Center instance URL (publicly accessible or network-reachable from Rootly)
  • A Jira account with the following permissions: Create Issues, Edit Issues, Assign Issues, Transition Issues, Close Issues, Link Issues
  • Username + password or a Personal Access Token
We recommend installing with a dedicated Jira service account so the integration does not break if an individual user leaves your organization.
If your Jira instance is in a private network, you must whitelist Rootly’s IP addresses before installation. See IP Allowlist below.

​
Installation

Open the Jira (On-Premise) integration in Rootly

Navigate to the integrations page in Rootly and select Jira (On-Premise).

Enter your instance details

Provide the following:Instance URL The base URL of your Jira Data Center instance (e.g. https://jira.yourcompany.com).Internal URL (optional) An internal network URL for Rootly to use when calling your instance. If set, Rootly uses this URL for API calls while displaying the public Instance URL in the UI.SSL Verify Mode (optional) Controls how Rootly verifies your instance’s SSL certificate. Leave blank to use the default (VERIFY_PEER). Options:
ModeBehavior
VERIFY_PEERDefault — verifies the server certificate
VERIFY_CLIENT_ONCEVerifies the client certificate only once
VERIFY_FAIL_IF_NO_PEER_CERTFails if no peer certificate is provided
VERIFY_NONEDisables certificate verification
Only use VERIFY_NONE if your instance uses a self-signed certificate in a trusted internal network. Disabling verification exposes you to man-in-the-middle attacks.

Authenticate

Provide either a username + password or a Personal Access Token — not both.
  • Username + Password — use your Jira Data Center account credentials
  • Personal Access Token — generate a PAT from your Jira profile under Profile > Personal Access Tokens
Rootly automatically refreshes Personal Access Tokens when they are within 5 days of expiry. Tokens are assumed to have a 30-day lifetime.
Select Connect to validate the connection and complete installation.
After installation, the same workflow actions available for Jira Cloud are available for your on-premise instance: Create a Jira Issue, Create a Jira Subtask, and Update a Jira Issue.

​
IP Allowlist

If your Jira instance is hosted in a private network or behind a firewall, allowlist the following Rootly IP addresses so our servers can reach your instance:
  • 34.232.217.139
  • 18.213.181.255

​
Workflow Actions

The Jira On-Premise integration shares the same workflow actions as Jira Cloud. Refer to the Jira Cloud documentation for the full reference on:
  • Create a Jira Issue
  • Create a Jira Subtask
  • Update a Jira Issue
When configuring workflow actions, select your on-premise instance from the Account dropdown.

​
Troubleshooting

Verify that your instance URL is publicly accessible or that Rootly’s IP addresses (34.232.217.139 and 18.213.181.255) are allowlisted in your firewall. Confirm the URL includes the correct port if your instance does not run on the default HTTPS port.
If your instance uses a self-signed or internal CA certificate, try setting the SSL Verify Mode to VERIFY_NONE as a temporary test. For production use, configure your instance with a certificate that Rootly can verify, or use VERIFY_PEER with a certificate from a trusted CA.
Confirm the token has not expired and that it was generated by a user with the required Jira permissions. If the token was recently rotated, update the integration credentials in Rootly under Configure.

​
Uninstall

To remove the Jira On-Premise integration, open the integrations panel in Rootly and select Configure > Delete. Removing the integration disables any internal workflows associated with this instance.