This page contains solutions targeted for administrators.

Use the FAQ below to find answers to common questions.  Feel free to contact our support team ( if you don't see what you're looking for.

Administration Questions

1. How do I let people browse Git securely but without defining Git IDs for everyone?

With the Git Integration for Jira add-on, you only need to define a single ID for the Jira server.  Jira then lets authorized Jira users browse Git.

You can restrict access to the Repository Browser (views git list/repo folders in Jira) for the selected repository by associating the project permissions.  On Jira, the View Development Tools permission must be granted to Users / Group / Project Roles.

Configure this setting via:

  • Jira dashboard > Git > Manage repositories > Actions > Edit integration/repository settings > Project Permissions.  Deselect All Projects checkbox and set one or two projects.
  • Connect Wizard > Integration Settings > Project Permissions.   Deselect All Projects checkbox and set one or two projects.
2. Does the Git Integration for Jira add-on have API commands that allow addition/removal of a Git project?

Yes.  As of v2.8.3 of the Git add-on, the REST API for add, update, and delete repository is implemented.  The documentation for this feature is available at Git add-on: Hook and API Reference - Repository REST API open in new tab.

3. After upgrading Jira from 4.1.1 to 5.2.9, I get some errors "Folder ... FORNEOnlineSolver git doesn't exist".  Where can I set the path correctly?  Is there any properties file?

Please visit add-on config and check Git Repositories tab.  Also upgrade of Jira may lead to changing of user account used to run service, which in turn, may result in lack of permissions.

4. Does Jira+GitHub integration support multiple Jira projects (many) to multiple git repositories (many)?  If it does not, how about many-to-one or one-to-many?

Yes — it does support repositories supporting many projects.  That said – the associations are made by the developers when they commit code to a specific issue key (which is part of a project).  The permission that allows a user to see these commits in a Jira project is whether they have the "View Development Tools" permission for that project (that's a Jira setting).

The only project permissions that the Git Integration for Jira add-on has are for the Repository Browser (Git dropdown menu).  To associate a repository with all Jira projects or only specific projects, see Repository Browser setting open in new tab in the Connect to Git Repository wizard or edit a repository in the Git Repositories configuration page.

5. How do I connect to HTTPS repositories with self signed SSL certificates or other SSL issues?

This problem may be caused by a custom (a self-signed) certificate.  Make sure to install the latest JRE and then change the JAVA_HOME of Jira server.

The above solution should work, otherwise, see below for the steps to workaround this issue:

  1. From your Jira Server, clone the repository manually using the git client.
  2. Example:
    cd /jira/home
    cd data/git-plugin
    git clone --mirror https://my-self-signed-repo/project.git
  3. Make sure that the Jira user has access to the folder above.
  4. Configure the repository to disable verification of the SSL certificate.
  5. Example:
    cd project.git
    git config http.sslVerify false
    Run git config http.sslVerify false in the repository folder.
  6. From your browser, log into Jira and add a repository via Administration > Add-ons/Applications (Jira 7).
  7. Select Git Repositores under Git Integration for Jira.
  8. Click Connect to Git Repository then Advanced setup.
  9. For the Display Name, enter a description of the Git repository.
  10. For the Repository Root, enter the full path to the Git repository that you have cloned.  Considering the example in step 1, it will be similar to /jira/home/data/git-plugin/project.git.
  11. Click the Detect button next to the Repository Origin.
  12. Click Add to add this repository to the Git repository configuration list.

The clone will be kept up-to-date and the SSL verification issues will be ignored.

There are alternative solutions to make Java trust this certificate.  Please refer to the following articles from Atlassian which focuses on helping to resolve SSL Verification Issues:

If the problem persist, please send us a support zip to give us a better view of the issue.

6. I want to track all repositories hosted in my GitLab server from my Jira Server.  How do I configure the required NFS access permissions?

Where a GitLab server is configured with NFS server and the Jira Server is configured with NFS client, there are two possible solutions:

Solution 1.

The 'all_squash' option must not be used in the NFS server 'etc/exports' file for GitLab folders.  The NFS client should have the 'git' group with the same GID as the 'git' group on the NFS server.  The Jira user on the NFS client should be added to the group 'git'.

Example of '/etc/exports' line:
/var/opt/gitlab/git-data/repositories/testrepo xx.xx.xx.xx/24(ro,root_squash,async)

Solution 2.

Use the 'all_squash,async,anonuid=$uid,anongid=$gid' option on NFS server, where $uid and $gid are user ID and group ID for 'git' user and 'git' group respectively (or another user/group which you are using to access GitLab repositories on GitLab server).

Example of '/etc/exports' line:
/var/opt/gitlab/git-data/repositories/testrepo xx.xx.xx.xx/24(ro,all_squash,async,anonuid=497,anongid=497)

In both cases either 'ro' or 'rw' options may be used on NFS server.