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

Contact Support
GitKraken Status  

Pull or merge requests (Development panel)

The Pull Requests (GitHub or other connected git hosts) or Merge Requests (if GitLab is connected) section lists the merge/pull requests and their status. All merge/pull requests from all types of sources are shown here (for now, GitLab/GitHub/Azure/TFS/VSTS).

The displayed information depends on which supported git hosts are connected to Jira. For example:

  • GitLab integrations only  –  merge requests

  • Other integrations  –  pull requests

  • Both GitLab and GitHub integrations  –  separate sections for merge requests and pull requests

For necessary permissions that GitLab users must have for creating pull/merge requests, see GitLab Documentation: Permissions.

This function does not work for connected single git repositories. Use the auto-connect integration instead.


Getting started

If a git host is connected to Jira, create a pull/merge request by clicking Create pull request or Create merge request label link on the Git integration panel. The following dialog is displayed:

  • Select Repository from the list.

    GITHUB If there are several repositories with the same name, the listed GitHub repositories will have their names attached with a GitHub organization name. For example, BigBrassBand/second-webhook-test-repo.

    GITLAB If there are several repositories with the same name, the listed GitLab repositories will have their names attached with a GitLab owner name. For example, johnsmith/second-webhook-test-repo.

  • Choose a branch as the Source branch. This branch will be merged to the Target branch.

  • Set master as the Target branch.

  • Enter a descriptive Title for this pull/merge request or leave it as is (recommended).

  • Click Create to finish this process.


If the Require User PAT option is enabled in Integration Settings and a user PAT isn’t configured yet for the selected repository via Repository Browser, the dialog below is displayed instead:


If an invalid PAT was configured for the selected repository, the pull/merge request creation process will fail.

This feature is available on connected GitLab1 and GitHub2 git hosts for Jira Server; GitLab, GitHub, Microsoft TFS/VSTS and AWS CodeCommit git hosts for Jira Cloud.


GitLab merge request

If you want to create a merge request for GitLab, click Create merge request. It has the same process described in the pull request creation steps above.

The merge request is displayed on the developer panel and will also be associated to the mentioned Jira issue by fulfilling the following condition:

  • A merge request Title must contain the issue key. For example, TEST-1-Fix-binaries.

This will also allow a service user to associate a Merge/Pull Request with multiple Jira issues regardless of commit associations.

We recommends service users to enable pull/merge requests webhook trigger events. This way, any changes to pull/merge requests gets reindexed quickly.

The Pull/merge request list provides status information about the pull/merge request if it is opened or merged. Hover the mouse pointer on the pull/merge request label to see information of the repository and branch where it belongs.

For detailed information on this feature, see Creating pull/merge requests.


Video Guide


Right click here to open this video in a new browser tab for more viewing options.

Associating pull or merge request to Jira issue

A git service user can create a PR/MR via the Git host service portal and adding/inserting a Jira issue key in the PR/MR title. This is automatically added to the Pull/Merge request list in the Jira issue Git developer panel.

Git service portal
Jira issue PR/MR list view

Additionally, creating PR/MR via the Git Integration developer panel automatically associates the PR/MR to a Jira issue. This also adds a description in the PR/MR to the git host service portal containing the link to the Jira issue.


Prev: Branches (Development panel)

Next: Git tags

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