diff options
author | GitLab Bot <gitlab-bot@gitlab.com> | 2023-09-01 15:09:50 +0300 |
---|---|---|
committer | GitLab Bot <gitlab-bot@gitlab.com> | 2023-09-01 15:09:50 +0300 |
commit | 02f6aecd47c847bb2a7d101678813fe5077ae299 (patch) | |
tree | 886df070fd7a3b3f0d364e879b89ea5eb31aeada /doc/user | |
parent | 5ffb2b7bcde1c76f939c5dca2ff65bac3404a88f (diff) |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/user')
-rw-r--r-- | doc/user/analytics/index.md | 31 | ||||
-rw-r--r-- | doc/user/project/settings/index.md | 13 | ||||
-rw-r--r-- | doc/user/search/index.md | 23 |
3 files changed, 26 insertions, 41 deletions
diff --git a/doc/user/analytics/index.md b/doc/user/analytics/index.md index 800a8a73855..9e99d9aeaaf 100644 --- a/doc/user/analytics/index.md +++ b/doc/user/analytics/index.md @@ -46,16 +46,6 @@ You can use GitLab to review analytics at the project level. Some of these featu - [Repository](repository_analytics.md) - [Value Stream Management Analytics](../group/value_stream_analytics/index.md), and [Value Stream Management Dashboard](value_streams_dashboard.md) -### Remove project analytics from the left sidebar - -By default, analytics for a project are displayed under the **Analyze** item in the left sidebar. To remove this item: - -1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Settings > General**. -1. Expand **Visibility, project features, permissions**. -1. Turn off the **Analytics** toggle. -1. Select **Save changes**. - ## User-configurable analytics The following analytics features are available for users to create personalized views: @@ -73,17 +63,10 @@ You can use the following analytics features to analyze and visualize the perfor ## Glossary -We use the following terms to describe GitLab analytics: - -- **Mean Time to Change (MTTC):** The average duration between idea and delivery. GitLab measures -MTTC from issue creation to the issue's latest related merge request's deployment to production. -- **Mean Time to Detect (MTTD):** The average duration that a bug goes undetected in production. -GitLab measures MTTD from deployment of bug to issue creation. -- **Mean Time To Merge (MTTM):** The average lifespan of a merge request. GitLab measures MTTM from -merge request creation to merge request merge (and closed/un-merged merge requests are excluded). -For more information, see [Merge Request Analytics](merge_request_analytics.md). -- **Mean Time to Recover/Repair/Resolution/Resolve/Restore (MTTR):** The average duration that a bug -is not fixed in production. GitLab measures MTTR from deployment of bug to deployment of fix. -- **Velocity:** The total issue burden completed in some period of time. The burden is usually measured -in points or weight, often per sprint. For example, your velocity may be "30 points per sprint". GitLab -measures velocity as the total points or weight of issues closed in a given period of time. +| Metric | Definition | Measurement in GitLab | +| ------ | ---------- | --------------------- | +| Mean Time to Change (MTTC) | The average duration between idea and delivery. | From issue creation to the issue's latest related merge request's deployment to production. | +| Mean Time to Detect (MTTD) | The average duration that a bug goes undetected in production. | From deployment of bug to issue creation. | +| Mean Time To Merge (MTTM) | The average lifespan of a merge request. | From merge request creation to merge request merge (excluding closed and unmerged merge requests). For more information, see [Merge Request Analytics](merge_request_analytics.md). | +| Mean Time to Recover/Repair/Resolution/Resolve/Restore (MTTR) | The average duration that a bug is not fixed in production. | From deployment of bug to deployment of fix. | +| Velocity | The total issue burden completed in some period of time. The burden is usually measured in points or weight, often per sprint. | Total points or weight of issues closed in a given period of time. Expressed as, for example, "30 points per sprint". | diff --git a/doc/user/project/settings/index.md b/doc/user/project/settings/index.md index b29456a259d..93661f041f9 100644 --- a/doc/user/project/settings/index.md +++ b/doc/user/project/settings/index.md @@ -283,7 +283,18 @@ To restore a project marked for deletion: 1. Expand **Advanced**. 1. In the Restore project section, select **Restore project**. -## Add a compliance framework to a project **(PREMIUM ALL)** +## Remove project analytics from the left sidebar + +By default, [analytics for a project](../../analytics/index.md#project-level-analytics) are displayed under the **Analyze** item in the left sidebar. +To remove this item: + +1. On the left sidebar, select **Search or go to** and find your project. +1. Select **Settings > General**. +1. Expand **Visibility, project features, permissions**. +1. Turn off the **Analytics** toggle. +1. Select **Save changes**. + +## Add a compliance framework to a project **(PREMIUM)** You can [add compliance frameworks to projects](../../group/compliance_frameworks.md#add-a-compliance-framework-to-a-project) diff --git a/doc/user/search/index.md b/doc/user/search/index.md index 408503f47ca..8c7db5ca29e 100644 --- a/doc/user/search/index.md +++ b/doc/user/search/index.md @@ -33,6 +33,9 @@ All global search scopes are enabled by default on self-managed instances. ## Global search validation +> - Support for partial matches in issue search [removed](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/71913) in GitLab 14.9 [with a flag](../../administration/feature_flags.md) named `issues_full_text_search`. Disabled by default. +> - [Generally available](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/124703) in GitLab 16.2. Feature flag `issues_full_text_search` removed. + Global search ignores and logs as abusive any search that includes: - Fewer than two characters @@ -47,6 +50,10 @@ Global search only flags with an error any search that includes more than: - 4096 characters - 64 terms +Partial matches are not supported in issue search. +For example, when you search issues for `play`, the query does not return issues that contain `display`. +However, the query matches all possible variations of the string (for example, `plays`). + ## Autocomplete suggestions As you type in the search box, autocomplete suggestions are displayed for: @@ -159,22 +166,6 @@ To search for a commit SHA: If a single result is returned, GitLab redirects to the commit result and gives you the option to return to the search results page. -## Search for specific terms - -> - [Support for partial matches in issue search](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/71913) removed in GitLab 14.9 [with a flag](../../administration/feature_flags.md) named `issues_full_text_search`. Disabled by default. -> - [Generally available](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/124703) in GitLab 16.2. Feature flag `issues_full_text_search` removed. - -You can search issues and merge requests for specific terms. -For example, when you search issues for `display bug`, the query returns -all issues that contain both `display` and `bug` in any order. -To search for the exact string, use `"display bug"` instead. - -Partial matches are not supported in issue search. -For example, when you search issues for `play`, the query does not return issues that contain `display`. -However, the query matches all possible variations of the string (for example, `plays`). - -For more information about query validation, see [Global search validation](#global-search-validation). - ## Run a search from history You can run a search from history for issues and merge requests. Search history is stored locally |