On 7th September we'll be releasing some new UI components for working with tickets (Our generic name for Jira tickets, ADO work items, Linear issues, etc) in Pipelines.

However, this is more than a UI refresh. In the past, Gearset didn't actually know which PRs were linked to which tickets. We needed to make a call to the VCS and do some processing every time we wanted this information.

This approach was inefficient, relatively slow and relied on a good connection to a healthy VCS. The new UI will instead rely on a Gearset-managed store containing these PR to ticket links.

The old UI also had separate components for each ticket system. This contributed to making adding a new system a significant undertaking. The new UI uses a unified set of components that work regardless of the ticket system(s) being used.

The new system relies on Gearset maintaining a record of the tickets referenced by a particular PR. VCSs don't have a robust way of giving us this information, so we need to parse it from text descriptions. In order to verify that the ticket references we find are real, we need to check that they actually exist in the ticket system.

This check is performed using the team-shared ticket system connection (or the pipeline owner's connection for user-owned pipelines). This means that the relevant connection must exist and must have permissions to access any tickets that any pipeline user might want to see. If not, the tickets it can't access will not be visible via Gearset.

This is a significant change to the old system, which barely made use of team-shared ticket connections at all. So, you may well need to create or update your ticket system connection in order for this to work correctly.

Once this improvement is in place, it will open up a whole set of features that we've been repeatedly asked for over the past couple of years: