Skip to main content
All CollectionsAutomationPipelinesTeam-shared Pipelines
Which Jira credentials are used for which actions in Pipelines?
Which Jira credentials are used for which actions in Pipelines?

Expected behaviour for the use of individual versus team-shared Jira credentials during automated Pipeline use.

Vincent Maltby avatar
Written by Vincent Maltby
Updated over a week ago

When using a team-shared automated Pipeline, you have the option to use team-shared Jira credentials.

However, we don't always use the team-shared credentials to update Jira for actions completed in the pipeline, and this article confirms what to expect.

Individual Jira credentials:

  • A person merges a pull request inside of a Gearset pipeline, that users individual Jira connection will be used to post the comment to any linked Jira tickets.

  • If an action in the pipeline is user initiated, this will use their personal Jira credentials.

  • If an action is automated in the pipeline (such as updating the Jira ticket status as a user story progresses between pipeline environments), this will use the users personal Jira connection credentials.

Team-shared Jira credentials:

  • A user merges a pull request but does not have their own personal Jira connection, the team shared connection is used to post the comment to any linked Jira tickets.

  • If a user merges a pull request outside of the pipeline, the pipeline owner's Jira connection is used. For a team shared pipeline, this is the team shared Jira connection.

Think of an action that isn't documented here? Please be sure to let our in-app support know!

Did this answer your question?