- Jira users can be required to provide their own Personal Access Token when creating a branch or pull request. See Require Personal Access Tokens for user actions (create branch/pull request) for instructions on how to configure this feature.
- The View developer tools permission is required to view the Git integration development panel (see more in Jira Issue Git integration development panel). Jira users must also have the Browse Project permissions to a project associated with a repository to view.
- Creating pull/merge request feature can be disabled for all Jira users (regardless of permissions) in General settings.
GitLab uses the term Merge Request rather than Pull Request (used by the other major git services). In the following article, Pull Request and Merge Request can be used interchangeably.
This feature is not available to single repository connections.
The Create pull/merge request feature offers Jira users the ability to create a git pull request directly from the Jira issue.
For information about creating a branch from a Jira issue, see Creating branches.
When creating a pull request from within Jira:
Automatically populates the pull request title with issue key (necessary for pull request ⇿ Jira issue association) and issue summary.
Require each Jira user to provide their Personal Access Token for creating pull requests. This option adds some friction to creating pull requests/branches but enabling this setting will enforce the git server user permissions as well as give better attribution for the actions. See Require Personal Access Tokens for user actions (create branch/pull request) for more information.
Full feature (Auto-connect) integrations:
Microsoft Visual Studio Team Services (VSTS)
Microsoft Team Foundation Server (TFS)
Steps to creating a git pull request in Jira
Prerequisite: Jira administrator configures a full feature (auto-connect) integration in the Git Integration for Jira Data Center app. See Integration guides for more information.
To access the Create pull request action, do one of the following:
Click Create pull request in one of the panels from step 2.
Select git repository. Use the search box to look for the specific name of the repository that will be used.
Select source branch.
Select target branch.
Verify pull request title is correct. Edit as desired.
Note: the Jira issue key must remain in the pull request name to create the pull request ⇿ Jira issue association.
Video: Creating pull/merge request from Git integration development panel ( UPDATED VIDEO COMING SOON )
The video shows Git Integration for Jira Cloud process but is also applicable to the Jira Server version.
Associating pull/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 developer panel automatically associates the PR/MR to a Jira issue.
See more Git Integration for Jira app features
Indexing queue viewer (Git Integration for Jira Server/Data Center)
Deep Linking to the GitKraken Git client (Git Integration for Jira Server/Data Center)
Deep Linking into GitLens (Git Integration for Jira Server/Data Center)
Git Integration + Jira Automation (Jira Server | DC) (Git Integration for Jira Server/Data Center)
Creating branches (Git Integration for Jira Server/Data Center)
Creating pull/merge requests (this page)
Associate Pull/Merge Requests to Issues Based on Commits (Git Integration for Jira Server/Data Center)
Issue Git integration panel (Git Integration for Jira Server/Data Center)
Smart commits overview (Git Integration for Jira Server/Data Center)
Shared reindex queue between DC nodes (Git Integration for Jira Server/Data Center)
Enforced git permissions for Jira users (Git Integration for Jira Server/Data Center)