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) as well as the default Jira Cloud instance.

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

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.

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 afterwards users can set up connections to Jira with a few clicks.

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.