Skip to main content
Connecting to an on-premise version of Jira

This article will take you through the steps of connecting a Self-hosted version of Jira to Gearset

Claudia McPhail avatar
Written by Claudia McPhail
Updated over a week ago

⚠️ As of the 15th of Feb. 2024, Atlassian has ended their technical support, security updates and bug fixes for vulnerabilities for their Server products. Before connecting to an on-premise version of either BitBucket or Jira check whether your company already has a plan to migrate to the cloud hosted versions of these products.

Gearset's Jira integration will automatically post updates to Jira tickets when you run validations and deployments. These updates will contain a link back to the Gearset deployment report. This feature makes tracking the status of your user stories and support tickets faster and easier. We support both Jira Self-hosted (a.k.a. on prem) and the default Jira Cloud instance.

Connecting to the on-premise Jira server (administrator)

So Gearset can talk to your on-premise Jira server, your Jira administrator / networking team should ensure:

  1. The internal Jira server has a public DNS entry pointing to a public IP address for that host. See https://dnschecker.org

  2. It is set to accept connections from Gearset's static IP addresses

If you are using proxy authentication, note that Gearset needs to be able to speak to the Jira server directly, which will then kick off the OAuth flow without an additional authentication wall in front of it.

If your account uses 2FA, you may need to create a custom application password for Gearset to connect to your system.

To ensure a secure connection, Gearset will only connect using https and your server needs to be set up with a valid certificate from a CA. Self-signed certificates are not supported as they can't guarantee a secure connection.

Initial Jira setup (team owner)

First, you need your Jira administrator to create an application link in Jira itself, and authorize Gearset. Doing this provides a mechanism for Gearset to authenticate against Jira and post updates to tickets. This only has to be completed once, and afterward users can set up connections to Jira with a few clicks.

Connecting to your Jira instance

Under Source control and services you have the option to connect to various source control repositories and issue tracking services, including Jira.

If you click on the + Connect to Jira option on the right-hand side of the screen, you will be given the option to connect with either Jira Cloud or Jira Self-hosted.
​ 
You should take note of the Consumer key and Public key that are generated.

 
You can now follow the normal flow of setting up a Jira connection as detailed in our integrating with Jira document here. Select "Atlassian product" if prompted for the type of application you want to connect to.

Considerations when using a reverse proxy


If you:

  • Are using a reverse proxy to provide Gearset access to your Jira instance,

    and

  • The URL provided to Gearset (i.e. your reverse proxy URL) is not the same as Jira's base URL

Then the connection setup may fail when connecting Gearset to Jira due to the mismatch between the reverse proxy URL and Jira's base URL.

If this occurs you can set the Internal URL option to the same as the Base URL as defined with Jira's General Configuration page:

Jira Base URL settings

Jira Base URL configuration

Gearset Jira Self-hosted configuration with Internal URL matching Jira Base URL

Did this answer your question?