Gearset's Jira integration automatically posts updates to Jira tickets when you run validations and deployments, with a link back to the full report in Gearset. It makes tracking the status of your user stories and support tickets faster and easier.

Initial Jira setup (team owner)

To get started, you’ll need your Jira administrator to create an application link in Jira itself and your team owner to authorize Gearset. This provides a mechanism for Gearset to authenticate against Jira in order to post updates to tickets, and only has to be completed once. After this has been done, any subsequent users can set up a Jira connection in just a couple of clicks.

Step 1: Copy Gearset’s public key

  • [Note: you must be the owner of your Gearset team to complete these steps]
  • In the resulting dialog, select Connect to Jira. Keep the generated public key and consumer key to hand as you'll need them for Step 2

Step 2: Creating an application link in Jira

  • In a new tab, sign in to your Jira instance as an administrator and navigate to the dashboard page [Note: this must be completed in a new tab to preserve the generated consumer key]. Then go to Jira settings > Products > Application links

 

  • Paste Gearset’s URL into the application URL text box, and click create new link:
  • When prompted with a dialog to confirm the application URL, click continue:

  • In the link applications dialog, fill in the application name and application type. It's important to leave the service provider name blank and to check create incoming link before clicking continue.

  • In the link applications dialog, enter the consumer name and Gearset’s consumer key and public key from Step 1. Once the configuration is complete, click continue:
  • Once completed, Gearset should appear as an application link in your Jira instance

Step 3: Authorize your Gearset to post on behalf of your Jira user

  • In Gearset, navigate to the connections page, switch to the source control tab and click connect to jira under manage linked services
  • Enter the URL of your Jira Cloud instance or Jira Self-hosted (on-prem) instance and click connect:
  • Upon clicking connect, you’ll be redirected to your Jira instance and prompted to log in, if you aren’t already. When prompted, grant Gearset permission to make changes to your Jira data by clicking allow:
  • Once complete, Jira will redirect you back to Gearset. 

Connecting to Jira (team members)

Once the Jira application link has been created and Gearset has been authorized by the team owner, the rest of the team members will be able to connect to Jira:

  • Navigate to the connections page, switch to the source control and Jira tab and click connect to Jira under manage linked services
  • Click allow within the Welcome to Jira dialogue box (as shown above)
  • You'll be redirected back to Gearset and can start linking Jira tickets

Adding a Jira ticket

Once you have set up an application link in Jira, you and your team can start linking Jira tickets to your deployments and validations. For Gearset to automatically update your Jira ticket, simply add the Jira ticket reference before you deploy or run a validation. 

  • To link a Jira ticket, follow the usual comparison process, selecting which metadata items you would like to deploy or include in your validated package. 
  • Once the pre-deployment problem analysis has checked for any potential issues, you’ll be taken to the summary of objects to deploy page. 
  • Click on the Jira updates tab, add in your ticket reference, and you’re all set! When adding ticket references you can search ticket titles or descriptions to find the ones you need. From there you can either validate and schedule the deployment or deploy instantly as usual. 

Within Jira, any actions performed will have been automatically recorded for you in your Jira ticket. 

Any deployment notes added to your deployment will also appear as comments attached to your Jira ticket.

If you wanted to configure the messages posted to Jira, here are some additional config settings that you can access via the Preferences cog.

You can also set the status of the Jira ticket directly from Gearset. Note that the status update that it only triggers on a successful deployment 


With this feature you’ll be able to see exactly what changes have been made at each step of the user story, making it easier to review changes and speed up your release cycles.

Did this answer your question?