Getting started for Git administrators

Welcome Git Admin!

You are probably reading this page because a Jira administrator has requested access to the Git server. The Jira administrator has installed the Git Integration for Jira app.

What’s on this page:


What is the Git Integration for Jira app?

The Git Integration for Jira app pulls data from a Git source code control repository. Jira users will be able to see code in Git in context with Jira projects and issues. Even non-technical users will be able to see Git in the familiar Jira interface.

Jira users will be able to securely browse content in Git without requiring you to create IDs for every user.

How does Jira interact with the Git server?

The Git Integration for Jira app acts as a regular Git client. It performs a scheduled pull from the repository.

What does the Jira administrator need?

The Jira administrator needs the ability to clone the repository and pull from it just like a regular developer workstation would do.

We recommend that you create a new user identity specifically for this Jira server.

For Git repositories with HTTP/HTTPS access

Please do the following:

  1. Create a new user for the Jira server.

  2. Send the Jira administrator:

  • The URL to the Git server

  • For example:  https://gitserver/repo/timetrackingproject.git

  • The username and password for the user you created

For Git repositories with SSH access

Please do the following:

  1. Define a new SSH public/private key pair for the Jira server

  2. Install the public key on the Git server

  3. Send the Jira administrator:

  • The URL to the Git server

  • For example:  git@gitserver:repo/timetrackingproject.git

  • The private key you created

For Git repositories with Git protocol access

Send the Jira administrator the URL to the Git server.

For example:  git://gitserver/repo/timetrackingproject.git

Troubleshooting issues

For information on troubleshooting known errors and issues, see Git Integration for Jira - Knowledge Base/FAQ and Troubleshooting guides.

Classic and webhook indexing

Classic indexing refers to an internal process which runs in a set amount of time to review repositories eligible to be checked for changes. For more information on how this works, see Classic indexing explainer.

Webhook indexing refers to automatic indexing designed to record changes in a timely manner for all types of repositories resulting in immediate reindex times. For more information on how this works, see Webhook indexing explainer.

 


Get new product notifications and feature updates from BigBrassBand LLC.

Get new product notifications and feature updates from BigBrassBand LLC.

Need to know more features?  Read next:  Helpful Tips for Jira Administrators