Use theif you have set up the Git repository ahead of time outside of the Jira Git Integration app. Configure repositories via in order to manage advanced options.
Open the Connect to Git Repository wizard then click thelabel.
On the Connect to Git Repository screen that appears, you will see the repository configuration page with several options for connection and advanced integration settings. Utilize the following options for adding new git repositories:
Display Name – This
is the name that will appear in the Git Integration app repositories list. (Required)
Some integrations does not allow the display name to be changed. On Jira Cloud, the ability to change the display name is not available.
|Cloned Repository Root|
|Absolute Repository Root – The absolute path of the cloned repository root is displayed here. (Read-only)|
|Cloned root location – Select manual or automatic configuration.|
|Repository Root – This is the local path to the repository on the server where your Jira service is running. This will point the Git Integration app to a clone of the repository hosted locally with Jira. (Required)|
Git repository hosted on remote server – In this mode, fetches are enabled using any external source. The reindex background service will initiate the fetch then add the new commits to the plugin index.
Git repository hosted on same server as Jira – Fetches are enabled when the repository is hosted locally. In this mode, no fetches are made. The reindex service runs in the background and process every new commit found.
This is the URL to the hosted git service used on the project. For example, you might host your repository on GitHub, Beanstalk or your own server.
The repository origin may not be hosted on the same server as Jira.
Main Branch – Specified branch will intend to
organize the git commit tab. A
commit will not be shown in other branches if it is a part of
the main branch. By default, "master" will be used if a main
branch is not specified.
When editing or updating repository settings, this field will allow a user to select from a list of available branches to assign as master for the selected repository configuration.
|Use HTTP(S) Authentication|
Most git hosts provide HTTP access to git repositories. If this connection
requires HTTP authentication, enable the option and enter the
required credentials to configure remote git repositories.
For Advanced settings, see description below.
|Revision Indexing – This option turns on the memory cache which is used when list of commits are displayed. Select if revision indexing will index and link to any mentioned issue keys in the revision history or not.|
Revision Cache Size –
This is the size of the memory cache. If some particular commit
is not cached, it is fetched from the Lucene index which
involves some disk activity.
Enter the number of revisions to keep the cache in memory. The default value is 10000. Higher values can affect the performance of the retrieved revisions from Git.
|Enables or disables the Git Viewer feature for this repository. The default setting for this option is Enabled. Users must have the View Development Tools project permission in order to use this feature. Consult your Jira System Administrator on permissions. For more information, see section, The Repository Browser.|
Show all tags – This will display all the tags for the specific issue.
Show tags matching the pattern – This will display tags on issue pages that match the specified regular expression pattern.
This example is a filtering regexp for a range of releases from 2.7.x to 2.8.x. The sidebar will display git tags for release versions 2.7.0 to 2.8.x in decending order.
Restrict to projects – One or more
projects must be mapped to this repository to make Git Commits tabs available in the Issue pages of the associated
This field requires at least one existing project if the Repository Browser for this repository is enabled.
|Associate with all projects – Enable this option to associate this repository to all projects. Disable this option if you want to use existing mapped projects from the Restrict to projects field. The default setting is enabled (checked).|
JIRA SERVER DATA CENTERClick Advanced to enable/disable limitation of commits shown in Git Commits issue tab, Git Commits page and all across the Git Integration for Jira app by project association.
This only applies when project associations are set. If the Associate with all projects option is enabled, this feature is ignored.
If this option is enabled for a git repository and there are project associations set, the git data is not shown from that repository in any project except those from the project associations list.
Unless the issue is from a project association list, some data are not shown such as:
This option defaults to true when setting new project associations.
Limit git data - upgrade and installation defaults:
|Commit View Options|
When enabled, this setting allows Jira users with the View Development Tools and correct Jira/Git Integration for Jira app permissions to view the commit and file diffs inside Jira.
This setting is enabled by default (as of v2.6.3 of the Git Integration app). See section, Smart Commits
Send notifications – Enables or disables commit notification emails for this repository.
Max. commit age in minutes – Set the desired value in minutes, as to when commit notifications will be sent. Commit notifications will be e-mailed if the age of the commit is less than or equal to this value.
The web linking feature adds links to your git hosting provider directly into
the Git Commits tab.
The Weblinking configuration is optional.
While Weblinking is automatically configured for most git hosts,For more information about this option, see section, Weblinking.
Click Add to save the settings. The newly added repository appears on the git repositories list of the add-on.
Repositories created via thewill perform an initial reindex.