License requirements:
Ticket tracking in Pipelines is available on Deployment Teams and Deployment Enterprise licenses.
Pipelines shows linked tickets on features, pull requests, and releases. You can link a ticket when you create a feature, or add one to a pull request later.
To link a ticket when you create a feature, see Configuring ticket tracking in Pipelines.
Where do linked tickets show in my pipeline?
The feature sidebar shows the tickets attached to a feature. A feature with one ticket shows its reference, and a feature with several shows a count.
Bundles will also show the tickets from all of the features combined in the same place.
The same tickets show as pills when you click
Commit more changeson an existing feature.
If you can't access a ticket, Gearset shows its reference only. To see its details, add a personal connection to that ticket system.
Releases
When adding Pull Requests into Releases the tickets will combine and show in the Tickets tab in the Pull Request. As shown below:
How do I link a ticket to an existing pull request?
Open the pull request details.
In the ticket section, click the
add ticketbutton.
Select the provider that has the ticket you want to add.
Click
Add.
The linked ticket now shows in the pull request details.
What if my tickets don’t show correctly on a pull request?
Check that the pipeline’s ticket system connection exists. See Ticket system connections and permissions in Pipelines.
In the pull request’s ticket section, click the refresh button:
How does Gearset link tickets to my pull requests?
Gearset reads ticket references from the pull request title and description. It doesn’t read references from the branch name.
Can I make my team link a ticket?
Yes. Turn on Require issue tracking in the Deployment settings on your My account page. Each pull request and Compare and Deploy deployment then needs a linked ticket.
Note: This setting currently works for Jira issues and Azure DevOps work items and Asana Tasks (Compare and Deploy) only.
