debian-mirror-gitlab/doc/integration/jira/index.md

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

114 lines
6.6 KiB
Markdown
Raw Normal View History

2021-04-29 21:17:54 +05:30
---
2021-10-27 15:23:28 +05:30
stage: Ecosystem
group: Integrations
2021-04-29 21:17:54 +05:30
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
---
# Jira integrations **(FREE)**
If your organization uses [Jira](https://www.atlassian.com/software/jira) issues,
2021-11-18 22:05:49 +05:30
you can [migrate your issues from Jira](../../user/project/import/jira.md) and work
2021-04-29 21:17:54 +05:30
exclusively in GitLab. However, if you'd like to continue to use Jira, you can
integrate it with GitLab. GitLab offers two types of Jira integrations, and you
2021-12-11 22:18:48 +05:30
can use one or both depending on the capabilities you need. We recommend you enable both.
2021-04-29 21:17:54 +05:30
2021-09-30 23:02:18 +05:30
## Compare integrations
2021-04-29 21:17:54 +05:30
After you set up one or both of these integrations, you can cross-reference activity
in your GitLab project with any of your projects in Jira.
2021-09-30 23:02:18 +05:30
### Jira integration
2021-04-29 21:17:54 +05:30
2021-10-27 15:23:28 +05:30
This integration connects one or more GitLab projects to a Jira instance. The Jira instance
2021-11-18 22:05:49 +05:30
can be hosted by you or in [Atlassian cloud](https://www.atlassian.com/migration/assess/why-cloud).
2021-09-30 23:02:18 +05:30
The supported Jira versions are `v6.x`, `v7.x`, and `v8.x`.
2021-04-29 21:17:54 +05:30
2021-09-30 23:02:18 +05:30
<i class="fa fa-youtube-play youtube" aria-hidden="true"></i>
For an overview, see [Agile Management - GitLab-Jira Basic Integration](https://www.youtube.com/watch?v=fWvwkx5_00E&feature=youtu.be).
2021-04-29 21:17:54 +05:30
2021-11-11 11:23:49 +05:30
To set up the integration, [configure the settings](configure.md) in GitLab.
2021-04-29 21:17:54 +05:30
### Jira development panel integration
The [Jira development panel integration](development_panel.md)
connects all GitLab projects under a group or personal namespace. When configured,
relevant GitLab information, including related branches, commits, and merge requests,
displays in the [development panel](https://support.atlassian.com/jira-software-cloud/docs/view-development-information-for-an-issue/).
2021-11-11 11:23:49 +05:30
To set up the Jira development panel integration, use the GitLab.com for Jira Cloud app
or the Jira DVCS (distributed version control system) connector,
[depending on your installation](development_panel.md#configure-the-integration).
2021-09-30 23:02:18 +05:30
2021-04-29 21:17:54 +05:30
### Direct feature comparison
2021-12-11 22:18:48 +05:30
| Capability | Jira integration | Jira development panel integration |
2021-04-29 21:17:54 +05:30
|-|-|-|
| Mention a Jira issue ID in a GitLab commit or merge request, and a link to the Jira issue is created. | Yes. | No. |
2021-10-27 15:23:28 +05:30
| Mention a Jira issue ID in GitLab and the Jira issue shows the GitLab issue or merge request. | Yes. A Jira comment with the GitLab issue or MR title links to GitLab. The first mention is also added to the Jira issue under **Web links**. | Yes, in the issue's [development panel](https://support.atlassian.com/jira-software-cloud/docs/view-development-information-for-an-issue/). |
| Mention a Jira issue ID in a GitLab commit message and the Jira issue shows the commit message. | Yes. The entire commit message is displayed in the Jira issue as a comment and under **Web links**. Each message links back to the commit in GitLab. | Yes, in the issue's [development panel](https://support.atlassian.com/jira-software-cloud/docs/view-development-information-for-an-issue/) and optionally with a custom comment on the Jira issue using Jira [Smart Commits](https://confluence.atlassian.com/fisheye/using-smart-commits-960155400.html). |
2021-04-29 21:17:54 +05:30
| Mention a Jira issue ID in a GitLab branch name and the Jira issue shows the branch name. | No. | Yes, in the issue's [development panel](https://support.atlassian.com/jira-software-cloud/docs/view-development-information-for-an-issue/). |
| Add Jira time tracking to an issue. | No. | Yes. Time can be specified using Jira Smart Commits. |
| Use a Git commit or merge request to transition or close a Jira issue. | Yes. Only a single transition type, typically configured to close the issue by setting it to Done. | Yes. Transition to any state using Jira Smart Commits. |
2021-11-18 22:05:49 +05:30
| Display a list of [Jira issues](issues.md#view-jira-issues). | Yes. | No. |
| Create a Jira issue from a [vulnerability or finding](../../user/application_security/vulnerabilities/index.md#create-a-jira-issue-for-a-vulnerability). | Yes. | No. |
2021-10-27 15:23:28 +05:30
| Create a GitLab branch from a Jira issue. | No. | Yes, in the issue's [development panel](https://support.atlassian.com/jira-software-cloud/docs/view-development-information-for-an-issue/). |
2021-04-29 21:17:54 +05:30
## Authentication in Jira
2021-12-11 22:18:48 +05:30
The authentication method in Jira depends on whether you host Jira on your own server or on
2022-06-21 17:19:12 +05:30
[Atlassian cloud](https://www.atlassian.com/migration/assess/why-cloud):
2021-04-29 21:17:54 +05:30
- **Jira Server** supports basic authentication. When connecting, a **username and password** are
2021-12-11 22:18:48 +05:30
required. Connecting to Jira Server using the Central Authentication Service (CAS) is not possible. For more information, read
2021-04-29 21:17:54 +05:30
how to [set up a user in Jira Server](jira_server_configuration.md).
- **Jira on Atlassian cloud** supports authentication through an API token. When connecting to Jira on
Atlassian cloud, an email and API token are required. For more information, read
2021-12-11 22:18:48 +05:30
[create an API token for Jira in Atlassian cloud](jira_cloud_configuration.md).
2021-04-29 21:17:54 +05:30
2021-06-08 01:23:25 +05:30
## Privacy considerations
2021-09-30 23:02:18 +05:30
If you integrate a private GitLab project with Jira using the [**Jira integration**](#jira-integration),
2021-06-08 01:23:25 +05:30
actions in GitLab issues and merge requests linked to a Jira issue leak information
about the private project to non-administrator Jira users. If your installation uses Jira Cloud,
2021-09-30 23:02:18 +05:30
you can use the [GitLab.com for Jira Cloud app](connect-app.md) to avoid this risk.
2021-06-08 01:23:25 +05:30
2021-12-11 22:18:48 +05:30
## Third-party Jira integrations
Developers have built several third-party Jira integrations for GitLab that are
listed on the [Atlassian Marketplace](https://marketplace.atlassian.com/search?product=jira&query=gitlab).
2021-04-29 21:17:54 +05:30
## Troubleshooting
If these features do not work as expected, it is likely due to a problem with the way the integration settings were configured.
2021-12-11 22:18:48 +05:30
### GitLab cannot comment on a Jira issue
2021-04-29 21:17:54 +05:30
2021-10-27 15:23:28 +05:30
If GitLab cannot comment on Jira issues, make sure the Jira user you
set up for the integration has permission to:
- Post comments on a Jira issue.
- Transition the Jira issue.
2021-04-29 21:17:54 +05:30
Jira issue references and update comments do not work if the GitLab issue tracker is disabled.
2021-12-11 22:18:48 +05:30
### GitLab cannot close a Jira issue
If GitLab cannot close a Jira issue:
2021-04-29 21:17:54 +05:30
2021-12-11 22:18:48 +05:30
- Make sure the `Transition ID` you set in the Jira settings matches the one
your project needs to close an issue.
2021-04-29 21:17:54 +05:30
2021-12-11 22:18:48 +05:30
- Make sure the Jira issue is not already marked as resolved:
- Check the Jira issue resolution field is not set.
- Check the issue is not struck through in Jira lists.
2021-04-29 21:17:54 +05:30
### CAPTCHA
2021-10-27 15:23:28 +05:30
CAPTCHA may be triggered after several consecutive failed login attempts,
2021-04-29 21:17:54 +05:30
which may lead to a `401 unauthorized` error when testing your Jira integration.
If CAPTCHA has been triggered, you can't use Jira's REST API to
2021-10-27 15:23:28 +05:30
authenticate with the Jira site.
To fix this error, sign in to your Jira instance
2021-04-29 21:17:54 +05:30
and complete the CAPTCHA.