Pipelines reads ticket details through one connection per pipeline. For a team-shared pipeline, this is the team-shared connection. For a user-owned pipeline, this is the pipeline owner's connection.
That connection must exist, and it must have access to every ticket that any pipeline user wants to see. Pipelines doesn't show tickets the connection can't access.
Why can't I see tickets in my pipeline?
Gearset checks that each ticket a PR references exists in your ticket system. It does this check with the pipeline's connection, not with each user's own connection.
Check that the connection exists. For a team-shared pipeline, check the team-shared connection. For a user-owned pipeline, check the pipeline owner's connection.
If the connection is missing, add it. See Connecting a ticket system to Gearset.
If the connection exists, check that it has access to all the tickets your pipeline users need.
If you can't give a team member's connection access to every project, use a service account for the team-shared connection instead.
Which connection does Gearset use for each action?
This table lists the connection Gearset uses for each ticket action in Pipelines.
Action | Connection used |
Read ticket details | Team-shared connection (team-shared pipeline) or the pipeline owner's connection (user-owned pipeline). |
Attach a ticket to a feature | The user's personal connection. |
Comment on a ticket when a user promotes a PR | That user's personal connection, if it can access the ticket. Otherwise, the pipeline owner's connection (the team-shared connection for a team-shared pipeline). |
Comment on a ticket when a PR is merged outside the pipeline | The pipeline owner's connection (the team-shared connection for a team-shared pipeline). |
Automated actions, such as a status update | The user's personal connection. |
Note: If ticket-status updates are required then the pipeline-owner connection user must have write/update permission on the applicable tickets.
What permissions does each ticket system need?
Jira
Jira
Gearset requests these Jira Cloud OAuth 2.0 scopes:
read:jira-workto search for and read projects, issues, and comments.read:jira-userto read your user profile, so updates are attributed to your account.write:jira-workto post comments on tickets and update statuses.
The Jira account behind the pipeline's connection must also have access to every Jira project your pipeline users work in.
Azure DevOps
Azure DevOps
The account behind the pipeline's connection needs read and write access to work items in every project your pipeline uses. Gearset reads work items, projects, and statuses, posts comments, and updates statuses.
Salesforce objects
Salesforce objects
Create a permission set for the service user with these permissions:
System Permissions > View Setup and Configuration, so Gearset can read your org information
Object Settings > your ticketing object > Read, Edit, and View All Records
Read access to the fields that hold the record ID and title
Read access to the status field, or edit access if Gearset updates the status
Linear
Linear
The account behind the pipeline's connection needs access to every Linear team whose issues your pipeline uses.
The user will need read access on the workspace and teams they have joined.