Gearset

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

Enable ticket tracking in each pipeline that uses your ticket system. You can then select a ticket when you create a feature, and Gearset names the feature branch from it.

Connect your ticket system first. See <a href="https://docs.gearset.com/en/articles/17338885-connecting-a-ticket-system-to-gearset">Connecting a ticket system to Gearset</a>.

How do I enable ticket tracking in my pipeline?

Click the cog icon, then select <code>Edit pipeline details...</code>.

Select your ticket system: <code>Jira</code>, <code>Azure DevOps</code>, <code>Linear</code>, or <code>Salesforce Tickets</code>.

Edit pipeline window with Issue tracking selected, showing Jira, Azure DevOps, Linear, and Salesforce Tickets.

If you selected Azure DevOps, select your organization. See the Azure DevOps section below. Jira, Linear, and Salesforce Tickets need no other settings.

1. Open your pipeline.
2. Click the cog icon, then select <code>Edit pipeline details...</code>.
3. Go to <code>Issue tracking</code>.
4. Select your ticket system: <code>Jira</code>, <code>Azure DevOps</code>, <code>Linear</code>, or <code>Salesforce Tickets</code>.
 
 Edit pipeline window with Issue tracking selected, showing Jira, Azure DevOps, Linear, and Salesforce Tickets.
 
5. If you selected Azure DevOps, select your organization. See the Azure DevOps section below. Jira, Linear, and Salesforce Tickets need no other settings.

Before you save, select your organization in <code>Azure organization for Work Items integration</code>. Each pipeline uses one organization, and you can only link work items from that organization. Gearset currently supports work items in Azure DevOps Cloud organizations only.

Edit pipeline window showing Azure DevOps settings, with an arrow pointing to the Azure organization dropdown.

To add a second ticket system, click <code>Connect another issue tracker</code>.

Edit pipeline window showing Jira settings, with an arrow pointing to Connect another issue tracker.

To update ticket statuses as work moves through the pipeline, see <a href="https://docs.gearset.com/en/articles/17338894-updating-a-ticket-s-status-in-pipelines">Updating a ticket's status in Pipelines</a>.

In your pipeline, click your developer sandbox.

In <code>Provider</code>, select the ticket system for the feature.

Select one or more tickets. You can select up to 10 tickets from the same ticket system. Use the filters or <code>Search for a ticket</code> to find them. You can <a href="https://docs.gearset.com/en/articles/17338890-using-tickets-in-pipelines#h_03f70cd0f5">add more tickets</a> later.

Check the branch name. Gearset fills it in from the tickets, using your feature branch format, and you can edit it.

Compare your sandbox to the feature branch, select your changes, and click <code>Commit changes</code>.

1. In your pipeline, click your developer sandbox.
2. Click <code>New feature</code>.
3. In <code>Provider</code>, select the ticket system for the feature.
4. Select one or more tickets. You can select up to 10 tickets from the same ticket system. Use the filters or <code>Search for a ticket</code> to find them. You can <a href="https://docs.gearset.com/en/articles/17338890-using-tickets-in-pipelines#h_03f70cd0f5">add more tickets</a> later.
 
 
 
5. Click <code>Continue</code>.
6. Check the branch name. Gearset fills it in from the tickets, using your feature branch format, and you can edit it.
7. Compare your sandbox to the feature branch, select your changes, and click <code>Commit changes</code>.

The linked tickets shows on the feature branch, and in the PR details after you create a pull request.

<a href="https://docs.gearset.com/en/articles/17338885-connecting-a-ticket-system-to-gearset">Connecting a ticket system to Gearset</a>

<a href="https://docs.gearset.com/en/articles/17338890-using-tickets-in-pipelines">Using tickets in Pipelines</a>

<a href="https://docs.gearset.com/en/articles/17338894-updating-a-ticket-s-status-in-pipelines">Updating a ticket's status in Pipelines</a>

<a href="https://docs.gearset.com/en/articles/6166062-promoting-your-first-features-in-gearset-pipelines">Promoting your first features in Gearset Pipelines</a>

<a href="https://docs.gearset.com/en/articles/8516723-starting-with-your-user-story-and-creating-feature-branches-in-pipelines">Starting with your user story and creating feature branches in Pipelines</a>

- <a href="https://docs.gearset.com/en/articles/17338885-connecting-a-ticket-system-to-gearset">Connecting a ticket system to Gearset</a>
- <a href="https://docs.gearset.com/en/articles/17338890-using-tickets-in-pipelines">Using tickets in Pipelines</a>
- <a href="https://docs.gearset.com/en/articles/17338894-updating-a-ticket-s-status-in-pipelines">Updating a ticket's status in Pipelines</a>
- <a href="https://docs.gearset.com/en/articles/6166062-promoting-your-first-features-in-gearset-pipelines">Promoting your first features in Gearset Pipelines</a>
- <a href="https://docs.gearset.com/en/articles/8516723-starting-with-your-user-story-and-creating-feature-branches-in-pipelines">Starting with your user story and creating feature branches in Pipelines</a>

How to enable Jira, Azure DevOps, Salesforce, or Linear ticket tracking in a pipeline and link tickets to features.

Configuring ticket tracking in Pipelines

No tickets or conversations found

Try selecting a different creation date range.

Tickets and conversations you've started through the messenger will appear here.

No tickets or conversations created by you

Try using different keywords or checking for typos.

Try selecting a different update date range.

Find answers and get help from Intercom Support and Community Experts

Conversations you've started through the messenger will appear here.

No conversations created by you

No conversations found

AI title

Title

This site employs cookies and other technologies that we and our third party vendors use to monitor and record personal information about you and your interactions with the site (including content viewed, cursor movements, screen recordings, and chat contents) for the purposes described in our Cookie Policy. By continuing to visit our site, you agree to our {websiteTermsLink}, {privacyPolicyLink} and {cookiePolicyLink}.

This site uses cookies and similar technologies ("cookies") as strictly necessary for site operation. We and our partners also would like to set additional cookies to enable site performance analytics, functionality, advertising and social media features. See our {cookiePolicyLink} for details. You can change your cookie preferences in our Cookie Settings.

We use cookies to make our site work and also for analytics and advertising purposes. You can enable or disable optional cookies as desired. See our {cookiePolicyLink} for more details.

Advertising cookies are set by our advertising partners to collect information about your use of the site, our communications, and other online services over time and with different browsers and devices. They use this information to show you ads online that they think will interest you and measure the ads' performance. Social media cookies are set by social media platforms to enable you to share content on those platforms, and are capable of tracking information about your activity across other online services for use as described in their privacy policies.

These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.

These cookies are necessary for the website to function and cannot be switched off in our systems.

These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site.

You have the right to opt out of the sale of your personal information. See our {cookiePolicyLink} for more details about how we use your data.

Your Privacy Choices

We use cookies to enhance your experience. You can customize your cookie preferences below. See our {cookiePolicyLink} for more details.

Cookie Settings

Empty Help Center

Uh oh. That page doesn’t exist.

Home

Search results

Disappointed

Neutral

Smiley

Thinking...

Searching through sources...

Analyzing...

Tickets submitted through the messenger or by a support agent in your conversation will appear here.

No tickets created by you

No tickets found

Conversations and tickets in {topic}

Conversations and tickets in {topic} // {subtopic}

Volume, creators and topics for your company.

Insights

Top creators

AI topics

Track the progress of all tickets and conversations related to your company.

Customer Portal.

Track the progress of all tickets related to your company.

Tickets portal.

{assigneeName} needs more information from you

Tickets

No access to tickets portal

You're not signed in on this browser. Sign in through this site's Messenger, then reload this page.

Sign in to view your company's tickets

Search

Skip the search. Describe what you’re trying to do and get a grounded answer.

Browse articles and guides in this topic.

Create your workspace and invite the people you work with.

Set up your account

Build your first workflow and watch it run end to end.

Ship something

Connect the tools your team already uses to bring data in.

Connect your stack

A quick lap of the product so you know where everything lives.

{appName} in 60 seconds

This prototype demo is aware that you are reading “{title}”. It can point you back to the current article, but a production article-aware Fin contract is still follow-up work.

Prototype article-aware answer

Because you already asked about invitations, this prototype demo can add the follow-up: use the role selector before sending each invite to limit access to the teammate responsibilities.

Prototype role-limiting follow-up

This prototype demo suggests starting with your workspace profile, inviting the team members who need access, and then connecting the integrations you use.

Prototype getting-started answer

In this prototype demo, integrations are configured from workspace settings. Choose the integration, connect the account, and review the enabled permissions.

Prototype integrations answer

In this prototype demo, invite teammates from workspace settings, then choose the access each teammate needs before sending the invitation.

Prototype invite-team answer

This prototype demo does not have a scripted answer for that question yet. Try asking how to invite your team or open a source article. No production Fin API was called.

Prototype answer unavailable

I’ve got this page open. Ask me anything about it and I’ll answer from the docs.

Configuring ticket tracking in Pipelines

How do I enable ticket tracking in my pipeline?

Azure DevOps: Select your organization

How do I create a feature from a ticket?

Useful resources