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:
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 .
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.
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 in the Connect to Git Repository wizard or edit a repository in the Git Repositories configuration page.
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:
cd /jira/home cd data/git-plugin git clone --mirror https://my-self-signed-repo/project.git
cd project.git git config http.sslVerify false
git config http.sslVerify falsein the repository folder.
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.
Where a GitLab server is configured with NFS server and the Jira Server is configured with NFS client, there are two possible solutions:
'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'.
'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).
In both cases either
'rw' options may be used on NFS server.