GitLab Jira development panel integration (FREE)

Moved from GitLab Premium to GitLab Free in 13.4.

With the Jira development panel integration, you can reference Jira issues in GitLab. When configured, activity (such as pipeline, deployment, and feature flags) displays in the Jira issue's development panel. From the development panel, you can open a detailed view and take various actions, including creating a new merge request from a branch:

The information displayed in the Jira development panel depends on where you mention the Jira issue ID:

Your mention of Jira issue ID in GitLab context	Automated effect in Jira issue
In a merge request title or description	Link to the MR is displayed in the development panel.
In a branch name	Link to the branch is displayed in the development panel.
In a commit message	Link to the commit is displayed in the development panel.
In a commit message with Jira Smart Commits	Displays your custom comment or logged time spent and/or performs specified issue transition on merge.

This integration connects all GitLab projects to projects in the Jira instance in either:

• A top-level GitLab group: Connects the projects in a group with no parent group, including the projects in its subgroups.
• A personal namespace: Connects the projects in that personal namespace to Jira.

Use the integration

After the integration is set up on GitLab and Jira, you can:

• Refer to any Jira issue by its ID (in uppercase) in GitLab branch names, commit messages, and merge request titles.
• See the linked branches, commits, and merge requests in Jira issues.
• Create GitLab branches from Jira Cloud issues (introduced in GitLab 14.2).

At this time, merge requests are called "pull requests" in Jira issues. This name may change in a future Jira release.

Select the links to see your GitLab repository data.

Use Jira Smart Commits

With Jira Smart Commits, you can use GitLab to add Jira comments, log time spent on the issue, or apply any issue transition.

For more information about using Jira Smart Commits to track time against an issue, specify an issue transition, or add a custom comment, read the Atlassian page Using Smart Commits.

Configure the integration

For an overview of how to configure the Jira development panel integration, see Agile Management - GitLab Jira development panel integration.

To simplify administration, we recommend that a GitLab group maintainer or group owner (or, if possible, instance administrator in the case of self-managed GitLab) set up the integration.

Jira usage	GitLab.com customers need	GitLab self-managed customers need
Atlassian cloud	The GitLab.com for Jira Cloud app installed from the Atlassian Marketplace. This offers real-time sync between GitLab.com and Jira. For more information, see the documentation for the GitLab.com for Jira Cloud app.	The GitLab.com for Jira Cloud app, using a workaround process. See the documentation for installing the GitLab.com for Jira Cloud app for self-managed instances for more information.
Your own server	The Jira DVCS (distributed version control system) connector. This syncs data hourly.	The Jira DVCS Connector.

Each GitLab project can be configured to connect to an entire Jira instance. That means after configuration, one GitLab project can interact with all Jira projects in that instance. For:

• The view Jira issues feature, you must associate a GitLab project with a specific Jira project.
• Other features, you do not have to explicitly associate a GitLab project with any single Jira project.

If you have a single Jira instance, you can pre-fill the settings. For more information, read the documentation for central administration of project integrations.

Limitations

This integration is not supported on GitLab instances under a relative URL. For example, http://example.com/gitlab.

Troubleshoot the development panel

If you use Jira on your own server, go to the Atlassian documentation for general troubleshooting information.

Cookies for Oracle's Access Manager

To support Oracle's Access Manager, GitLab sends additional cookies to enable Basic Auth. The cookie being added to each request is OBBasicAuth with a value of fromDialog.