diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2021-07-20 09:55:51 +0000 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2021-07-20 09:55:51 +0000 |
| commit | e8d2c2579383897a1dd7f9debd359abe8ae8373d (patch) | |
| tree | c42be41678c2586d49a75cabce89322082698334 /doc/integration/jira/issues.md | |
| parent | fc845b37ec3a90aaa719975f607740c22ba6a113 (diff) | |
| download | gitlab-ce-e8d2c2579383897a1dd7f9debd359abe8ae8373d.tar.gz | |
Add latest changes from gitlab-org/gitlab@14-1-stable-eev14.1.0-rc42
Diffstat (limited to 'doc/integration/jira/issues.md')
| -rw-r--r-- | doc/integration/jira/issues.md | 21 |
1 files changed, 9 insertions, 12 deletions
diff --git a/doc/integration/jira/issues.md b/doc/integration/jira/issues.md index 91311f85310..34ca5481b85 100644 --- a/doc/integration/jira/issues.md +++ b/doc/integration/jira/issues.md @@ -6,7 +6,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w # Jira integration issue management **(FREE)** -Integrating issue management with Jira requires you to [configure Jira](development_panel.md#configure-the-integration) +Integrating issue management with Jira requires you to [configure Jira](index.md#jira-integration) and [enable the Jira service](development_panel.md#configure-gitlab) in GitLab. After you configure and enable the integration, you can reference and close Jira issues by mentioning the Jira ID in GitLab commits and merge requests. @@ -49,13 +49,10 @@ You can [disable comments](#disable-comments-on-jira-issues) on issues. > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/280766) in [GitLab Ultimate](https://about.gitlab.com/pricing/) 13.12 behind a feature flag, disabled by default. > - [Deployed behind a feature flag](../../user/feature_flags.md), disabled by default. -> - Disabled on GitLab.com. -> - Not recommended for production use. -> - To use in GitLab self-managed instances, ask a GitLab administrator to [enable it](#enable-or-disable-the-ability-to-require-an-associated-jira-issue-on-merge-requests). **(ULTIMATE SELF)** - -This in-development feature might not be available for your use. There can be -[risks when enabling features still in development](../../user/application_security/index.md#security-approvals-in-merge-requests). -Refer to this feature's version history for more details. +> - [Enabled by default](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/61722) in GitLab 14.1. +> - Enabled on GitLab.com. +> - Recommended for production use. +> - For GitLab self-managed instances, GitLab administrators can opt to [disable it](#enable-or-disable-the-ability-to-require-an-associated-jira-issue-on-merge-requests). **(ULTIMATE SELF)** You can prevent merge requests from being merged if they do not refer to a Jira issue. To enforce this: @@ -125,7 +122,7 @@ Issues are grouped into tabs based on their - **Closed** tab: All issues with a Jira status categorized as Done. - **All** tab: All issues of any status. -## Search and filter the issues list +### Search and filter the issues list **(PREMIUM)** To refine the list of issues, use the search bar to search for any text contained in an issue summary (title) or description. Use any combination @@ -188,9 +185,9 @@ adding a comment to the Jira issue: ## Enable or disable the ability to require an associated Jira issue on merge requests The ability to require an associated Jira issue on merge requests is under development -and not ready for production use. It is deployed behind a feature flag that is -**disabled by default**. -[GitLab administrators with access to the GitLab Rails console](../../administration/feature_flags.md) can enable it. +but ready for production use. It is deployed behind a feature flag that is +**enabled by default**. +[GitLab administrators with access to the GitLab Rails console](../../administration/feature_flags.md) can opt to disable it. To enable it: |