The Git Integration for Jira app allows users of integrations (examples: GitLab, GitHub, etc) to create branches and pull requests from within the Jira issue. By default the operation will be performed by the integration user that is used for indexing.
For teams looking to maintain user attribution - Jira administrators can require that individual Jira users provide personal access tokens to perform actions (like creating a branch or pull request in Jira using their git service account - rather than the integration account).
User attribution is supported in the following special integrations in Git Integration for Jira Cloud:
Microsoft Azure DevOps
Microsoft Visual Studio Team Services (VSTS)
Microsoft Team Foundation Server (TFS)
To enable/disable the Require User PAT setting for all repositories within an integration:
Navigate to Manage Git repositories.
Add a new integration or edit existing integration's settings.
Locate the Require User PAT setting.
Check the box to require PAT option.
What will Jira users see?
Once the Jira administrator requires Personal Access Tokens - your Jira users will be presented with a message that setup is required.
With the Personal Access Token saved - the user will now see the following:
PATs were introduced with TFS 2017 and newer. TFS 2013 and TFS 2015 do not support PATs. If the repository setting Require User PAT property is set to ON, the users will not be able to create/delete branches and pull requests.
Personal Access Tokens are saved per integration by individual Jira users app. Examples shown above are for the Create branch action; Create pull request is the same. The same token is used for Create branch and Create pull request.
Jira users must have the View Development Tools permission in the context of a Jira project to view content from the Git Integration for Jira app.