doc/integration/jira/_index.md
{{< details >}}
{{< /details >}}
Connect your GitLab projects with Jira to maintain a streamlined development workflow across both platforms. When your team uses Jira for issue tracking and GitLab for development, Jira integrations make the connection between planning and execution.
With Jira integrations:
You can import your Jira issues to GitLab or integrate Jira with GitLab and continue to use both platforms together.
GitLab offers two Jira integrations. You can use one or both integrations depending on the features you need.
{{< history >}}
{{< /history >}}
You can use the Jira issues integration developed by GitLab with Jira Cloud, Jira Data Center, or Jira Server. With this integration, you can:
You can use the Jira development panel to view GitLab activity for an issue including related branches, commits, and merge requests. To configure the Jira development panel:
This table shows the features available with the Jira issues integration and the Jira development panel:
| Feature | Jira issues integration | Jira development panel |
|---|---|---|
| Mention a Jira issue ID in a GitLab commit or merge request, and a link to the Jira issue is created. | {{< icon name="check-circle" >}} Yes | {{< icon name="dotted-circle" >}} No |
| Mention a Jira issue ID in GitLab, and the Jira issue shows the GitLab issue or merge request. | {{< icon name="check-circle" >}} Yes, a Jira comment with the GitLab issue or merge request title links to GitLab. The first mention is also added to Web links in the Jira issue. | {{< icon name="check-circle" >}} Yes, GitLab merge requests are shown in the Jira issue's development panel. GitLab issues are not shown in the development panel. |
| Mention a Jira issue ID in a GitLab commit, and the Jira issue shows the commit message. | {{< icon name="check-circle" >}} Yes, the entire commit message is displayed in the Jira issue as a comment and in Web links. Each message links back to the commit in GitLab. | {{< icon name="check-circle" >}} Yes, in the Jira issue's development panel. A custom comment is possible with Jira Smart Commits. |
| Mention a Jira issue ID in a GitLab branch name, and the Jira issue shows the branch name. | {{< icon name="dotted-circle" >}} No | {{< icon name="check-circle" >}} Yes, in the Jira issue's development panel. |
| Add time tracking to a Jira issue. | {{< icon name="dotted-circle" >}} No | {{< icon name="check-circle" >}} Yes, with Jira Smart Commits. |
| Use a GitLab commit or merge request to transition a Jira issue. | {{< icon name="check-circle" >}} Yes, only a single transition. Typically used to close the Jira issue. | {{< icon name="check-circle" >}} Yes, transition the Jira issue to any state with Jira Smart Commits. |
| View a list of Jira issues. | {{< icon name="check-circle" >}} Yes | {{< icon name="dotted-circle" >}} No |
| Create a Jira issue for a vulnerability. | {{< icon name="check-circle" >}} Yes | {{< icon name="dotted-circle" >}} No |
| Create a GitLab branch from a Jira issue. | {{< icon name="dotted-circle" >}} No | {{< icon name="check-circle" >}} Yes, in the Jira issue's development panel. |
| Mention a Jira issue ID in a GitLab merge request, branch name, or any of the last 2,000 commits to the branch after the last successful deployment to the environment to sync a GitLab deployment to a Jira issue. | {{< icon name="dotted-circle" >}} No | {{< icon name="check-circle" >}} Yes, in the Jira issue's development panel. |
All Jira issues integrations share data outside of GitLab. If you integrate a private GitLab project with Jira, the private data is shared with users who have access to your Jira project.
The Jira issues integration posts GitLab data as comments on Jira issues. The GitLab for Jira Cloud app and the Jira DVCS connector share GitLab data through the Jira development panel. With the Jira development panel, you can restrict access to certain user groups or roles.