This process requires an existing GitLab git repository. For starters, the GitLab repository URL can be acquired on the repository project page. Choose between SSH or HTTPS.
Use this information to connect the GitLab git repository to your Jira Cloud via Git Integration for Jira add-on: Manage Git Repositories > Connect to Git Repository.
The Git Integration for Jira add-on supports v3 and v4 of the GitLab API (in both Jira Cloud and Jira Server).
This process requires an existing GitLab.com account. Multiple git repositories in a GitLab.com account will be connected via Git Integration for Jira add-on.
GitLab introduced personal access tokens (PAT) since version 8.8 and now (v10+) prefers this type of authentication for accessing the git repositories. Service users are strongly advised to switch from using username/password to using Personal Access Tokens (PAT) for GitLab.com.
While instructions from GitLab works just fine, here are some specific instructions to get you up and running.
There will be a slight delay in adding this repository compared to others. It will show in the git configuration list eventually.
curl --header "Private-Token: XpigzF1JxMnAZ7mn9qgN" https://gitlab.com/api/v4/projects?membership=true
This process requires a GitLab git repository and a PAT with
For GitHub Organization, the user must have the Write permissions and the
Perform a commit to the newly-created branch to be ready for merge.
The pull request feature works the same as merge request.
To create a merge request and merge it to the main source (master):
The merge request is listed on the developer panel of the Jira issue page.
The merge request is also ready for approval by the reviewers in your GitLab web portal.