diff options
Diffstat (limited to 'doc/integration/jira/issues.md')
| -rw-r--r-- | doc/integration/jira/issues.md | 30 |
1 files changed, 15 insertions, 15 deletions
diff --git a/doc/integration/jira/issues.md b/doc/integration/jira/issues.md index 086d478ac15..7ed9d3ab329 100644 --- a/doc/integration/jira/issues.md +++ b/doc/integration/jira/issues.md @@ -27,7 +27,7 @@ git commit -m "GIT-1 this is a test commit" GitLab adds to that Jira issue: -- A reference in the **Web links** section +- A reference in the **Web links** section. - A comment in the **Activity** section that follows this format: ```plaintext @@ -41,9 +41,9 @@ GitLab adds to that Jira issue: - `COMMENTLINK`: Link to where the Jira issue is mentioned. - `ENTITY_TITLE`: Title of the GitLab commit (first line), issue, or merge request. -Only a single cross-reference comment appears in Jira per GitLab issue, merge request, or commit. +Only a single cross-reference appears in Jira per GitLab issue, merge request, or commit. For example, multiple comments on a GitLab merge request that reference a Jira issue -create only a single cross-reference comment back to that merge request in Jira. +create only a single cross-reference back to that merge request in Jira. You can [disable comments](#disable-comments-on-jira-issues) on issues. @@ -55,8 +55,8 @@ You can [disable comments](#disable-comments-on-jira-issues) on issues. With this integration, you can prevent merge requests from being merged if they do not refer to a Jira issue. To enable this feature: -1. On the top bar, select **Main menu > Projects** and find your project. -1. On the left sidebar, select **Settings > Merge requests**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your project. +1. Select **Settings > Merge requests**. 1. In the **Merge checks** section, select **Require an associated issue from Jira**. 1. Select **Save**. @@ -79,8 +79,8 @@ When you don't configure custom rules, the [default behavior](https://gitlab.com To define a regex pattern for Jira issue keys: -1. On the top bar, select **Main menu > Projects** and find your project. -1. On the left sidebar, select **Settings > Integrations**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your project. +1. Select **Settings > Integrations**. 1. Select **Jira**. 1. Go to the **Jira issue matching** section. 1. In the **Jira issue regex** text box, enter a regex pattern. @@ -92,8 +92,8 @@ For more information, see the [Atlassian documentation](https://confluence.atlas To define a prefix for Jira issue keys: -1. On the top bar, select **Main menu > Projects** and find your project. -1. On the left sidebar, select **Settings > Integrations**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your project. +1. Select **Settings > Integrations**. 1. Select **Jira**. 1. Go to the **Jira issue matching** section. 1. In the **Jira issue prefix** text box, enter a prefix. @@ -138,8 +138,8 @@ provided your GitLab administrator [has configured the integration](configure.md To view Jira issues: -1. On the top bar, select **Main menu > Projects** and find your project. -1. On the left sidebar, select **Issues > Jira issues**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your project. +1. On the left sidebar, select **Plan > Jira issues**. The issues are sorted by **Created date** by default, with the most recently created issues listed at the top. @@ -173,10 +173,6 @@ of these filters: Enhancements to use these filters through the user interface [are planned](https://gitlab.com/groups/gitlab-org/-/epics/3622). -## Create a Jira issue for a vulnerability **(ULTIMATE)** - -You can create a Jira issue for a vulnerability from a [Vulnerability Page](../../user/application_security/vulnerabilities/index.md#create-a-jira-issue-for-a-vulnerability). - ## Automatic issue transitions > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/55773) in GitLab 13.11. @@ -217,3 +213,7 @@ adding a comment to the Jira issue: 1. Refer to the [Configure GitLab](configure.md) instructions. 1. Clear the **Enable comments** checkbox. + +## Related topics + +- [Create a Jira issue for a vulnerability](../../user/application_security/vulnerabilities/index.md#create-a-jira-issue-for-a-vulnerability) |