Connecting a ticket system to Gearset

License requirements:
Ticket tracking in Pipelines is available on Deployment Teams and Deployment Enterprise licenses.

Gearset connects to Jira, Azure DevOps, Salesforce objects tickets, Linear and Asana so you can link tickets to your work. Connect your ticket system once, then enable it in each pipeline that uses it.

In this article, a ticket means a Jira ticket, an Azure DevOps work item, a Salesforce record, a Linear issue, or an Asana task.

Note: Pipelines reads ticket details through the team-shared connection, or through the pipeline owner's connection for user-owned pipelines. Make sure that connection exists. See Ticket system connections and permissions in Pipelines.

How do I connect my ticket system?

In Gearset, go to My connections > Source control and services. As shown below:

Then you can click to add any of Jira, Azure DevOps, Linear or Asana. As shown:

And here in Team-shared services:

To connect Salesforce objects, see the Salesforce objects section below.

We recommend that you connect every ticket system with a team-shared connection that uses a service account. A service account only has the access that Gearset needs, and doesn’t depend on one team member’s account.

Note: Jira has deprecated OAuth 1.0a. If you still have an OAuth 1.0a Jira connection, connect with OAuth 2.0 and then remove the 1.0a connection.

Jira Cloud

Any Gearset user can connect Jira Cloud.

Click Connect to Jira (OAuth 2.0).
Select Jira Cloud, then click Connect.
On the Atlassian page, choose your Jira site and click Accept.

Gearset shows your email address next to the Jira OAuth 2.0 connection when the connection is set up.

Jira Data Center

Connecting self-hosted Jira Data Center takes two steps. First, a Jira administrator creates an incoming link. Then, your Gearset team owner connects Gearset to it.

Step 1: Create an incoming link in Jira Data Center

A Jira administrator does this step.

In Jira Data Center, go to Administration > Applications > Application links.
Click Create link.
Select External application, then select Incoming as the direction.
In Redirect URL, enter https://app.gearset.com/authorization/jira-oauth2/callback.
In Application permissions, select Write. Write includes Read, so this one permission gives Gearset all the access it needs.
Click Save.
Copy the Client ID and Client secret. Keep them safe. You need them in step 2.

Step 2: Connect in Gearset

The Gearset team owner does this step.

In Gearset, go to My connections > Source control and services.
Click Connect to Jira (OAuth 2.0).
Select Jira Data Center, then click Connect.
Enter your Jira Data Center instance URI, the client ID, and the client secret. Click Connect.
On your Jira Data Center page, review the permissions and click Approve.

Gearset shows the connection next to the Jira OAuth 2.0 section when it is set up.

How do team members connect?

After the team owner sets up the connection, each team member connects their own Jira account.

Go to My connections > Source control and services.
Click Connect to Jira (OAuth 2.0).
On your Jira Data Center page, approve access.

If the team owner hasn't set up the connection yet, Gearset shows a message. The message asks you to contact your team owner.

Note: If the team owner removes the Jira Data Center connection, Gearset also removes every team member's connection. A team member can remove their own connection without affecting anyone else.

Azure DevOps

Gearset supports work items in Azure DevOps Cloud organizations only. Azure DevOps Server (self-hosted) work items are not currently supported.

Connect Azure DevOps the same way you connect it for source control. See Integrating with Azure DevOps.

The user assigning the ticket will need to have a user owned connection.

Linear

Log in to your Linear workspace.
In Gearset, go to Source control and services.
Click Connect to Linear.
Review and authorize the connection on the Linear authorization screen.

Salesforce objects

Gearset links records from one Salesforce object to your work. The object can be a standard object, such as Cases, or a custom object, such as one installed by Agile Accelerator.

Note: Each team can use only one Salesforce org for ticket tracking.

In the ticketing org, create a permission set. For the permissions it needs, see Ticket system connections and permissions in Pipelines.
Create a service user and assign the permission set to it.
In Gearset, add the org as a team-owned connection with the service user. This limits Gearset’s access to the ticketing object, so Gearset doesn’t show other sensitive data from your org. See Managing Salesforce org connections.
Click the connection and select Issue Tracking (1). As shown below. If the org has scratch orgs enabled, you will need to open the dropdown using the three dots(2) which will show the Issue Tracking option.
Configure the listed properties and click Save.
Click Delegate access on the same connection.
Give at least Comparison access to every user who links or views Salesforce records.

Asana (Compare and Deploy only)

Asana is only currently available to be connected through a user-owned connection, not team connection.

Log in to your Asana workspace.
In Gearset, go to Source control and services.
Click Connect to Asana.
Review and authorize the connection on the Asana authorization screen.

What do I do next?

Next, check the permissions your connection needs, then enable ticket tracking in your pipeline: