General Settings Jira Server only

Change Git Integration for Jira add-on settings in the Add-on Management page (Applications page in Jira 7) to show/hide the Git Commits issue tab.

warning
Starting v2.5.9 of the Git Add-on, the option to enable/disable Git Commits issue tabs has been moved to the Add-on Management > Git Integration Plugin > General page.
Jira 7: Administration > Applications > Git Integration Plugin for Jira > General.

Go to cog Administration > Add-ons.  Under Git Integration Plugin for Jira, select General.

helpful tip
If using Jira 7, go to Administration  > Add-ons. Select Applications on the page tab. Under Git Integration Plugin for Jira on the sidebar, select General.
Git Roll Up Issue Tab
General setting Git Roll Up tab group
Do not display  –  This tab is not displayed on the Issue screen for all Jira projects.
Show for all projects  –  This tab will be displayed on the issue screen for all Jira projects.
Show for selected projects  –  This tab will only be displayed on selected projects.  Define one or more required projects into the textbox.
Git Commits Issue and Project Tabs
General setting Git issue/proj tab group
Do not display  –  This tab is not displayed on the Issue and Project screens for all Jira projects.
Show for all projects  –  This tab will be displayed on the issue and project screens for all Jira projects.
Show for selected projects  –  This tab will only be displayed on the issue and project screens on selected projects.  Define one or more required projects into the textbox.
Git issue updates, tags, activity stream, email notification
Jira Issue Updates
Enable/disable the setting to allow new commits to change the Last Updated field.  Default is enabled.  For more information about this setting, see section Reindexing – Reindex and updatedDate Filter.
tips
Disabling this setting will improve Jira performance.
Issue Git Source Code Panel
Show Git Source Code panel on issue pages  –  Enable/disable the setting to have Git Integration for Jira add-on show/hide the Git Source Code section on the Jira issue developer panel. General setting - Git Source Code panel
tips
Disabling this setting will improve Jira performance.
Calculate and show Git tags in Git Source Code panel  –  Enable/disable the setting to have Git Integration for Jira add-on calculate and show the Git tags in the Git Source Code panel.
For more information, see Git Tags.
tips
Disabling this setting will improve Jira performance.
JQL Searching Introduced  v2.12.0  
Enables/disables the ability to use the JQL functions within the Git Integration for Jira add-on.
The default state for new Git add-on installation is Enabled. This setting will be automatically enabled when doing an upgrade from previous versions of the Git Integration for Jira add-on.
tips
Disabling this setting will improve Jira performance.
Git Activity Stream
Enable/disable the setting whether to show git commits in the Jira activity stream (Issue page or dashboard widget) or not.
For in-place upgrade of the Git add-on, this setting is turned off by default.  For new installation, the default state is enabled.
tips
Disabling this setting will improve Jira performance.
General Settings git integration options and commit notification emails
Git Integration Options Introduced v2.13.1
These settings will take effect at integration level for projects with connected GitLab/GitHub git hosts.  The default state for each setting is enabled.
  • Enable branch creation  –  shows or hides the function for creating of branches.  The ability to delete selected branches from the Jira developer panel is dependent on this setting.
  • Enable pull/merge request creation  –  shows or hides the function for creating pull/merge requests from the Jira developer panel.
Set the Branch Name Template using the supported variables. Use the template to generate a default name for newly-created branches.
Use the following template variables:
  • ${issuekey} - Issue Key. Issue key is used in upper case.
  • ${summary} - Issue Summary. The Summary is used and will be in lowercase; spaces are substituted by "-".
  • ${projectkey} - Project Key. The Project key is used and will be in uppercase.
  • ${username} - The username is used when logging into Jira (e.g. johnsmith). The username will be in lowercase.
tips
For example, the Git add-on default is:
{issuekey}-${summary}
This generates the string format like "PRJ-123-add-more-logging" as a default value.  Where PRJ-123 is the issue key followed by a hyphen then the summary text of the active issue page (in hyphenated lowercase form).
Email Settings
General Settings email settings
Send commit notification emails  
Enable/disable the setting to allow sending of email notifications when a commit is made.  This setting defaults to OFF for Git add-on upgrades and ON for new installation of the Git add-on.  This setting also enables/disables email notifications related to smart commits.
In the provided box, enter a regular expression to send e-mail only to addresses that matches this pattern.  Leave this field blank to disable this filter.
For more information, see Commit Email Notifications.
tips
Disabling this setting will improve Jira performance.
Repository Reindexing
General Settings repository reindex and max open file count
Reindex interval  –  Set the automatic reindex interval frequency value in minutes as required.  Default value is 5 minutes.
Configuration of the scheduler jobs are no longer accessible in the Jira administration page.  For this case, the Git add-on offers Jira administrators this capability via the General screen.  Minimum value is 1.  Maximum value is 2147483647.  Only whole numbers are allowed.
Repositories (Max open pack files count)   Introduced v2.13.5
Max Open Pack Files count  –  Set the maximum number of open files the Git Integration for Jira add-on uses.  The default value for new Git add-on install or upgrade is 32.  This is the recommended value.  You may set this value higher but not exceeding the maximum number of open files allowed in the system.
tips
For systems that has a lot of connected repositories, increasing this value to a higher setting may improve the performance of the Git Integration for Jira add-on such as during repository browsing. This is also applicable to very busy systems that has large repository connections. Configure the maximum open files allowed by the system accordingly.
Repositories Garbage Collection checker
These settings control Git repositories garbage collection.  Garbage collection process will prune all loose objects, pack loose references and repack all reachable objects into new pack files and remove the old ones.
Git repository GC checker group
GC check interval  –  Set the number of minutes that will elapse before a repository is checked to see if it should be garbage collected.  The default value is 1440 minutes.
Max loose objects count  –  Set the maximum number of loose objects that will be checked before the garbage collection is triggered. The garbage collection is activated if the number of loose objects exceeds this setting. Loose objects are single items that are not compressed into a Git pack file. The default value is 2000.
Max packed files count  –  Set the maximum number of packed files that will be checked before the garbage collection is triggered. If the number of packed files count exceeds this setting, the garbage collection is activated. The default value is 30.
Maximum Diff Line Count 
General Settings Diff Limit and File encoding
Max Diff Line Count  –  Set the maximum size of diffs that is allowed to be displayed in the diff dialog.  Setting this option to a higher value will affect diff display performance.
File encoding Introduced v2.13.1
While the Git add-on uses default Jira System Encoding (utf-8) to deliver source files and diffs of repository, this setting is for those who have several repositories with source files encoded under different encodings.
Define one or more encoding type to use separated with comma.  For example, win-1252, win-1251, utf-8.
For a list of encodings, see Supported Encodings open in new tab.
Discard cloned files in Jira Home Directory  Beta feature  Introduced  v2.12.0
General Settings save storage for cloned repositories
This feature will reduce Jira server storage by deleting files from cloned git repositories after indexing.  Discarding files can save disk space but may limit some features such as displaying diffs of files.
There are three options to choose from:
  • Keep all cloned binary files. No storage savings. All features available  This option will leave all cloned repositories intact.
  • Discard all files that match the mask below. Some features limited.  This option will delete all files in the cloned repositories matching the declared file extensions.
  • Discard all files EXCEPT those that match the mask below. Some features limited.  This option will delete all other files in the cloned repositories except those files with extensions declared.
Select any option with the discard label to enable editing of the file mask field.
caution
Whenever the setting is changed, BigBrassBand recommends to perform a manual reclone of the repositories to ensure an error-free operation.
Git Operations Timeout  Introduced  v2.12.0
General Settings Git operations timeout
Timeout  –  Set the git operations timeout value in seconds.  The default value is 60 seconds.  This setting affects how long will Git Integration for Jira add-on waits for connections performed during git clone and git fetch.

Click Save to apply the changes.

fyi
The higher the change rate of the repository, the more often it would benefit from garbage collection.
note
Every git installation has global config file and .git/config file in every git repository. All settings at the global level can be overridden at the repository level. Therefore, different email addresses can be set for every git repository.
For more details on git configuration, see Customizing Git: Git Configuration open in new tab.