diff options
Diffstat (limited to 'doc/integration/jira/issues.md')
| -rw-r--r-- | doc/integration/jira/issues.md | 30 |
1 files changed, 16 insertions, 14 deletions
diff --git a/doc/integration/jira/issues.md b/doc/integration/jira/issues.md index f6716f49ea5..9385ec63373 100644 --- a/doc/integration/jira/issues.md +++ b/doc/integration/jira/issues.md @@ -1,7 +1,7 @@ --- stage: Manage group: Import and Integrate -info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments +info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments --- # Jira issue management **(FREE ALL)** @@ -67,12 +67,16 @@ Jira issue can't be merged. The merge request displays the message You can configure custom rules for how GitLab matches Jira issue keys by defining: -- [A regex pattern](#use-regular-expression) -- [A prefix](#use-a-prefix) +- [A regex pattern](#define-a-regex-pattern) +- [A prefix](#define-a-prefix) -When you don't configure custom rules, the [default behavior](https://gitlab.com/gitlab-org/gitlab/-/blob/710d83af298d8896f2b940faf48a46d2feb4cbaf/lib/gitlab/regex.rb#L552) is used. For more information, see the [RE2 wiki](https://github.com/google/re2/wiki/Syntax). +When you do not configure custom rules, the +[default behavior](https://gitlab.com/gitlab-org/gitlab/-/blob/9b062706ac6203f0fa897a9baf5c8e9be1876c74/lib/gitlab/regex.rb#L245) is used. -### Use regular expression +### Define a regex pattern + +You can use a regular expression (regex) to match Jira issue keys. +The regex pattern must follow the [RE2 syntax](https://github.com/google/re2/wiki/Syntax). To define a regex pattern for Jira issue keys: @@ -83,12 +87,14 @@ To define a regex pattern for Jira issue keys: 1. In the **Jira issue regex** text box, enter a regex pattern. 1. Select **Save changes**. -For more information, see the [Atlassian documentation](https://confluence.atlassian.com/adminjiraserver073/changing-the-project-key-format-861253229.html). +For more information, see the +[Atlassian documentation](https://confluence.atlassian.com/adminjiraserver073/changing-the-project-key-format-861253229.html). -### Use a prefix +### Define a prefix -You can define a prefix for GitLab to match Jira issue keys. For example, if your Jira issue ID is `ALPHA-1` -and you've set a `JIRA#` prefix, GitLab matches `JIRA#ALPHA-1` rather than `ALPHA-1`. +You can use a prefix to match Jira issue keys. +For example, if your Jira issue key is `ALPHA-1` and you define a `JIRA#` prefix, +GitLab matches `JIRA#ALPHA-1` rather than `ALPHA-1`. To define a prefix for Jira issue keys: @@ -140,7 +146,7 @@ provided your GitLab administrator [has configured the integration](configure.md To view Jira issues: 1. On the left sidebar, select **Search or go to** and find your project. -1. On the left sidebar, select **Plan > Jira issues**. +1. Select **Plan > Jira issues**. The issues are sorted by **Created date** by default, with the most recently created issues listed at the top. @@ -212,7 +218,3 @@ 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) |