Git branch author no the one who created it. Why?

[Peter Rivera]

Hi,

I just deployed Git integration for Jira and users are new to it. One user (User1) has created a Git branch from a ticket but when it is created, User1 is not the author of it, instead, it displays other user (User2).

My issue looks like this: https://community.atlassian.com/t5/Sourcetree-questions/Commit-Author-why-is-the-commit-author-not-me/qaq-p/605332

But we're using Azure DevOps instead.

Another issue is that it creates the branch under my account in Azure DevOps, think it might be because I used my own token to connect Git integration to Azure.

Is there a setting where a user creates a branch under the his name as the author and the owner of the branch in remote server (Azure)?

Thanks!

[Adam Wride · Accepted solution]

Hi Peter - 

Yes - there is a setting for Jira admins to require that each user enter their own Personal Access Token for actions like creating a branch or a pull request.

You will find this in the integration settings:

Then the Require User PAT setting:

Once you enable that your users will see this prompt when creating a branch/pull request (one-time setup):

Where they will be taken to the View all repositories screen. Clicking on the pencil/edit icon for the integration for the desired repository will show a dialog where they paste in their Personal Access Token from Azure DevOps.

Instructions: creating personal access tokens.

Cheers,

Adam

(For future readers - the current version of the Git Integration for Jira Server as of this posting is v3.1.10)

[Peter Rivera]

Hi Adam,

Thanks for the reply! It works now, however, we need to enable the Git repository browser first before doing that then disable once they configure their tokens. Giving a window time to access the repository by non-admins and non-dev users. Just a security concern but all is good.

Thank you for you support,

Peter

[Adam Wride]

Peter - 

Depending on your needs - it is possible to leave the Repository Browser enabled - but disable source code diff viewing (documentation). This setting does affect a variety of areas in the app so this approach may or may not work for your team.

Cheers,

Adam 

[Adam Wride]

This feature is documented here.