Edit the TSV file by referring to the parameters below:
Assign an ID number to a repository. This is required if you wish to update or edit existing repositories by setting this value to their equivalent IDs. If this field is left blank, the repository will be created as new.
When importing to a new server, the id field must be blank.
String. Optional on existing servers.
This is the local path to the repository on the server where your Jira service is running. This will point the Git Integration for Jira app to a clone of the repository hosted locally with Jira.
This field corresponds to the Repository root input box in the Advanced setup/Repository settings.
The realRoot field may refer to an existing repository on a new server. If "root" doesn't exist, this field must be blank.
If this field is specified, absoluteRoot must also be defined.
This field corresponds to the Cloned root location input field in the Advanced setup/Repository settings.
If set to true, the repository is automatically managed by Git Integration for Jira app (stored in $JiraHOME).
If set to false, the repository is manually configured by the Jira administrator.
If this field is specified, realRoot must also be defined.
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.
BigBrassBand recommends to use the git@<url>:[your-git-repo].git format for the repository origin URL and adding of SSH Keys for each git host in the Git Integration app configuration page.
For HTTPS git repositories, obtain the URL from your git host then set your login credentials in the username and password (or pat) field to connect to them.
The repository origin may not be hosted on the same server as Jira.
String. Optional. Some git hosts may require this to be filled in.
Define a meaningful name for this repository configuration. If this field is left blank, the default value is obtained from the origin.
Set to true to enable fetches on git repositories hosted on remote servers.
Set to false to enable fetches on git repositories hosted on the same server as Jira.
This setting turns on the memory cache which is used when list of commits are displayed. Set to true if revision indexing will index and link to any mentioned issue keys in the revision history or not (false).
Set specific branch as the main branch for this repository. The default value is "master".
These are numeric projects IDs associated with the repository.
This field accepts list of comma separated project IDs for project mapping. Trailing spaces are ignored (equivalent to unchecking the Associate to All Projects checkbox in the Advanced Setup dialog). Example:10000,10100
If you change an existing repository, leaving this field blank will use the existing values of the repository configuration.
Setting this field to ALL will retain projectMapping settings and sets "All Projects" flag to true (equivalent to checking the Associate to All Projects checkbox in the Advanced Setup dialog).
If projects are not associated to the repository, you must leave this field blank and set the gitViewerEnable field to false.
This setting is enabled by default. Enables/disables smart commits processing for this repository or tracked folder. The default value for this field is true.
Send commit notification emails for this repository. If left blank, the default value for this field is true.
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. Default value is 1440 minutes.
When the trustFolderStat setting is set to false, the .git/objects/pack folder will be always scanned to check for new pack files. If set to true, the last-modified attribute of the folder will be used to check the folder for modifications.
The default value for Jira Server is true.
If your repository is stored on a network share, it is highly recommended to set the trustFolderStat value to false.
Boolean. Optional. This is a reference to refs/notes/* used for fetching. The default value for this field is false.
Git notes are not shown…
when refs/notes are disabled on connecting a repository;
when a new note comes when refs/notes is disabled.
Boolean. Optional. This is a reference to refs/changes/* used for fetching. The default value for this field is false.
String. Optional. This is a user-defined list of references used for fetching. It is a comma-separated list with the format: +refs/refname1/*:refs/refname1/*, refs/refname2/*:refs/refname2/*, ...
Take note that the .tsv file is verified by the Git Integration for Jira app with the following rules:
The header row is required.
The order of fields specified in the header row – is the order of the fields in the following rows.
If a field is omitted from the header row, the Git Integration app will use the default value for a new repository. The Git Integration app will keep the current value of a repository if it already exists in the configured repositories.
If a repository is not listed in the .tsv file, no changes will be made if the same repository exists in the Git Integration app configuration.