Git Integration for Jira Self-Managed (Data Center/Server) Documentation

Contact Support
GitKraken Status  

General settings – Improving Jira performance

What’s on this page:



Access these settings via Jira dashboard menu Git ➜ Manage repositories ➜ (sidebar) General settings.


Improving Git tags performance

Git tags and branches are cached for the most recently viewed 1000 Jira issues (across all Jira projects). The cache is reset each time a new change in any repository is detected. The cache is built the first time an issue with a tag and/or branch is loaded by a user. Subsequent loading of Jira issues with tag or branch information will utilize cached values.

Enabling the display of Git tags in commits for large repositories can affect the performance of Jira. This setting can be disabled by doing the following steps:

  1. Go to Jira dashboard menu Git ➜ Manage repositories.

  2. On your sidebar under Git Integration for Jira, select General settings.

  3. Under Issue Git integration panel options, uncheck the Calculate and show Git tags in the Git Integration panel on issue pages setting.

  4. Click Save to save and apply the setting.


Improving diff load performance

There’s a default limit to the size of files that the diff’er supports which is 16MB. This is to keep a massive file from impacting the Jira server performance too much.

Jira administrators can control over the size of diffs allowed to be displayed in the code diff dialog:

  1. Go Jira dashboard menu Git ➜ Manage repositories.
  2. On the sidebar under Git Integration for Jira, select General settings.
  3. Scroll down to Diff then set the Max Diff Line Count value as desired. Maximum supported value is 20000.


Setting this value higher than the default value will impact the performance when loading the code diff of the selected file in the Git Commits tab. The code diff dialog will truncate the view for each 1500 lines code. To see the rest of the code, manually expand the view.

This setting prevents the display of huge diffs. Thus, improving Jira performance.


Enable or disable JQL search feature

On your dashboard menu, go to Git ➜ Manage repositories ➜ General settings (sidebar). (Alternatively, go to Jira Administration ➜ Applications ➜ General settings).

Enable/disable the JQL searching setting.

This general setting allows administrators to enable/disable the JQL functions within the Git Integration for Jira app.

Turn off this setting to improve Jira performance.


Smart commits setting

To improve performance, turn off smart commits on initial indexing then turn it back on after initial reindexing.

Commit Notification Emails

Enable/disable the setting to allow sending of email notifications when a commit is made. This setting defaults to OFF for upgrades and ON for new installation of the Git Integration for Jira app.

Turn off this setting to 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 Integration for Jira app, this setting is turned off by default. For new installation, the default setting is enabled.

Disabling this setting will improve Jira performance.


Prev: New GitLab v10+ authentication

Next: Adding a repository hosted on Windows Servers or Windows Network share (Admins)


More related articles on Git for Jira administrators

Setup GitLab Server to respond to incoming network API calls

New GitLab v10+ authentication

General settings: Improving Jira performance (this page)

Adding a repository hosted on Windows Servers or Windows Network Share (Admins)

Setting up repository root not located in Jira Home directory (Admins)

Reindex API to trigger indexing

Recommended reindex interval setting

Setting up web linking

Setting up webhooks

Increasing timeout threshold for large repositories while doing a Git pull

Working with Tracked folders

Recommended upgrade method for Git Integration for Jira

Discard cloned files in Jira Home directory (General setting)

Have feedback about this article? Did we miss something? Let us know!
On this page