From a7b3560714b4d9cc4ab32dffcd1f74a284b93580 Mon Sep 17 00:00:00 2001 From: GitLab Bot Date: Fri, 18 Feb 2022 09:45:46 +0000 Subject: Add latest changes from gitlab-org/gitlab@14-8-stable-ee --- doc/user/analytics/code_review_analytics.md | 2 +- .../img/issues_created_per_month_v13_11.png | Bin 21731 -> 0 bytes .../img/issues_created_per_month_v14_8.png | Bin 0 -> 17292 bytes .../img/mr_mean_time_to_merge_metric_v13_9.png | Bin 12299 -> 0 bytes .../analytics/img/mr_throughput_table_v13_3.png | Bin 20273 -> 0 bytes doc/user/analytics/issue_analytics.md | 2 +- doc/user/analytics/merge_request_analytics.md | 127 ++++++--------------- doc/user/analytics/productivity_analytics.md | 4 +- 8 files changed, 41 insertions(+), 94 deletions(-) delete mode 100644 doc/user/analytics/img/issues_created_per_month_v13_11.png create mode 100644 doc/user/analytics/img/issues_created_per_month_v14_8.png delete mode 100644 doc/user/analytics/img/mr_mean_time_to_merge_metric_v13_9.png delete mode 100644 doc/user/analytics/img/mr_throughput_table_v13_3.png (limited to 'doc/user/analytics') diff --git a/doc/user/analytics/code_review_analytics.md b/doc/user/analytics/code_review_analytics.md index 066b45aeb39..18a6ca20bc7 100644 --- a/doc/user/analytics/code_review_analytics.md +++ b/doc/user/analytics/code_review_analytics.md @@ -17,7 +17,7 @@ requests, and: - Take action on individual merge requests. - Reduce overall cycle time. -Code Review Analytics is available to users with at least the Reporter [role](../permissions.md), and displays a table of open merge requests that have at least one non-author comment. The review time is measured from the time the first non-author comment was submitted. +Code Review Analytics is available to users with at least the Reporter role, and displays a table of open merge requests that have at least one non-author comment. The review time is measured from the time the first non-author comment was submitted. NOTE: Initially, no data appears. Data is populated as users comment on open merge requests. diff --git a/doc/user/analytics/img/issues_created_per_month_v13_11.png b/doc/user/analytics/img/issues_created_per_month_v13_11.png deleted file mode 100644 index da3340bfdc2..00000000000 Binary files a/doc/user/analytics/img/issues_created_per_month_v13_11.png and /dev/null differ diff --git a/doc/user/analytics/img/issues_created_per_month_v14_8.png b/doc/user/analytics/img/issues_created_per_month_v14_8.png new file mode 100644 index 00000000000..7dcfa73ea19 Binary files /dev/null and b/doc/user/analytics/img/issues_created_per_month_v14_8.png differ diff --git a/doc/user/analytics/img/mr_mean_time_to_merge_metric_v13_9.png b/doc/user/analytics/img/mr_mean_time_to_merge_metric_v13_9.png deleted file mode 100644 index ad108dabf73..00000000000 Binary files a/doc/user/analytics/img/mr_mean_time_to_merge_metric_v13_9.png and /dev/null differ diff --git a/doc/user/analytics/img/mr_throughput_table_v13_3.png b/doc/user/analytics/img/mr_throughput_table_v13_3.png deleted file mode 100644 index bb63770dc3f..00000000000 Binary files a/doc/user/analytics/img/mr_throughput_table_v13_3.png and /dev/null differ diff --git a/doc/user/analytics/issue_analytics.md b/doc/user/analytics/issue_analytics.md index 6aa2f594532..62fff443073 100644 --- a/doc/user/analytics/issue_analytics.md +++ b/doc/user/analytics/issue_analytics.md @@ -34,7 +34,7 @@ You can change the total number of months displayed by setting a URL parameter. For example, `https://gitlab.com/groups/gitlab-org/-/issues_analytics?months_back=15` shows a total of 15 months for the chart in the GitLab.org group. -![Issues created per month](img/issues_created_per_month_v13_11.png) +![Issues created per month](img/issues_created_per_month_v14_8.png) ## Drill into the information diff --git a/doc/user/analytics/merge_request_analytics.md b/doc/user/analytics/merge_request_analytics.md index bb110ab495f..f9ca06c0ef9 100644 --- a/doc/user/analytics/merge_request_analytics.md +++ b/doc/user/analytics/merge_request_analytics.md @@ -1,119 +1,66 @@ --- -description: "Merge Request Analytics help you understand the efficiency of your code review process, and the productivity of your team." # Up to ~200 chars long. They will be displayed in Google Search snippets. It may help to write the page intro first, and then reuse it here. +description: "Merge request analytics help you understand the efficiency of your code review process, and the productivity of your team." # Up to ~200 chars long. They will be displayed in Google Search snippets. It may help to write the page intro first, and then reuse it here. stage: Manage group: Optimize 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 --- -# Merge Request Analytics **(PREMIUM)** +# Merge request analytics **(PREMIUM)** > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/229045) in GitLab 13.3. > - Moved to GitLab Premium in 13.9. -Merge Request Analytics helps you understand the efficiency of your code review process, and the productivity of your team. +Use merge request analytics to view: -## Overview +- The number of merge requests your organization merged per month. +- The average time between merge request creation and merge. +- Information about each merged merge request. -Merge Request Analytics displays information that will help you evaluate the efficiency and productivity of your merge request process. +You can use merge request analytics to identify: -The Throughput chart shows the number of merge requests merged, by month. Merge request throughput is -a common measure of productivity in software engineering. Although imperfect, the average throughput can -be a meaningful benchmark of your team's overall productivity. +- Low or high productivity months. +- Efficiency and productivity of your merge request process. +- Efficiency of your code review process. -To access Merge Request Analytics: +## View merge request analytics + +You must have at least the Reporter role to view merge request analytics. + +To view merge request analytics: 1. On the top bar, select **Menu > Projects** and find your project. 1. On the left sidebar, select **Analytics > Merge request**. -## Use cases +## View merge requests merged per month -This feature is designed for [development team leaders](https://about.gitlab.com/handbook/marketing/strategic-marketing/roles-personas/#delaney-development-team-lead) -and others who want to understand broad patterns in code review and productivity. +> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/232651) in GitLab 13.3. +> - Filtering [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/229266) in GitLab 13.4 -You can use Merge Request Analytics to expose when your team is most and least productive, and -identify improvements that might substantially accelerate your development cycle. +To view the number of merge requests merged per month: -Merge Request Analytics could be used when: - -- You want to know if you were more productive this month than last month, or 12 months ago. -- You want to drill into low- or high-productivity months to understand the work that took place. +1. On the top bar, select **Menu > Projects** and find your project. +1. On the left sidebar, select **Analytics > Merge request**. +1. Optional. Filter results: + 1. Select the filter bar. + 1. Select a parameter. + 1. Select a value or enter text to refine the results. + 1. To adjust the date range: + - In the **From** field, select a start date. + - In the **To** field, select an end date. -## Visualizations and data +The **Throughput** chart shows the number of merge requests merged per month. -The following visualizations and data are available, representing all merge requests that were merged in the given date range. +The table shows up to 20 merge requests per page, and includes +information about each merge request. -### Mean time to merge +## View average time between merge request creation and merge > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/229389) in GitLab 13.9. -The mean time to merge (MTTM) metric shows the average time between when a merge request is created, -and when it is merged. To view how the MTTM changes over time, compare MTTM across different date ranges. - -![Mean time to merge](img/mr_mean_time_to_merge_metric_v13_9.png "Merge Request Analytics - MTTM metric showing the average time it takes from initiating a MR to being merged") - -### Throughput chart - -The throughput chart shows the number of merge requests merged per month. - -![Throughput chart](img/mr_throughput_chart_v13_3.png "Merge Request Analytics - Throughput chart showing merge requests merged in the past 12 months") - -### Throughput table - -> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/232651) in GitLab 13.3. - -The Throughput table displays the most recent merge requests merged in the date range. The -table displays up to 20 merge requests at a time. If there are more than 20 merge requests, -you can paginate to them. For each merge request, you can review the following data: - -- Title (as a link to the merge request itself) -- ID -- Pipeline status -- Label count -- Comment count -- Approval count (if approved) -- Date merged -- Time to merge -- Milestone -- Commit count -- Pipeline count -- Line change counts -- Assignees - -![Throughput table](img/mr_throughput_table_v13_3.png "Merge Request Analytics - Throughput table listing the 100 merge requests most recently merged") +Use the number in **Mean time to merge** to view the average time between when a merge request is +created and when it's merged. -## Filter the data +To view **Mean time to merge**: -> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/229266) in GitLab 13.4 - -You can filter the data that is presented on the page based on the following parameters: - -- Author -- Assignee -- Label -- Milestone -- Source branch -- Target branch - -To filter results: - -1. Select the filter bar. -1. Select a parameter to filter by. -1. Select a value from the autocompleted results, or enter search text to refine the results. -1. Press Enter. - -## Date range - -The date range is set to the past 12 months by default. You can modify the date range by changing the "From" and/or "To" values that appear alongside the filter bar. After changing either value, the data displayed on the page will update automatically. - -## Tip: Bookmark preferred settings - -You can bookmark preferred filters and date ranges. After you have applied a change to the -filter bar or the date range, you'll see that information in the URL. You can create a -bookmark for those preferred settings in your browser. - -## Permissions - -The **Merge Request Analytics** feature can be accessed only: - -- On [GitLab Premium](https://about.gitlab.com/pricing/) and above. -- By users with at least the Reporter [role](../permissions.md). +1. On the top bar, select **Menu > Projects** and find your project. +1. On the left sidebar, select **Analytics > Merge request**. diff --git a/doc/user/analytics/productivity_analytics.md b/doc/user/analytics/productivity_analytics.md index e1ba2f5565e..be710f8cbd7 100644 --- a/doc/user/analytics/productivity_analytics.md +++ b/doc/user/analytics/productivity_analytics.md @@ -65,7 +65,7 @@ request is merged. Select the dropdown to view: The right-side histogram shows the size or complexity of a merge request. Select the dropdown to view: - + - Number of commits per merge request. - Number of lines of code (LOC) per commit. - Number of files touched. @@ -103,4 +103,4 @@ You can filter analytics based on a date range. To filter results: The **Productivity Analytics** dashboard can be accessed only: - On [GitLab Premium](https://about.gitlab.com/pricing/) and above. -- By users with at least the Reporter [role](../permissions.md). +- By users with at least the Reporter role. -- cgit v1.2.3