File: productivity_analytics.md

package info (click to toggle)
gitlab 17.6.5-19
  • links: PTS, VCS
  • area: main
  • in suites: sid
  • size: 629,368 kB
  • sloc: ruby: 1,915,304; javascript: 557,307; sql: 60,639; xml: 6,509; sh: 4,567; makefile: 1,239; python: 406
file content (67 lines) | stat: -rw-r--r-- 2,934 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
---
stage: Plan
group: Optimize
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
---

# Productivity analytics

DETAILS:
**Tier:** Premium, Ultimate
**Offering:** GitLab.com, Self-managed, GitLab Dedicated

You can use productivity analytics to identify:

- Your development velocity based on how long it takes for a merge request to merge.
- The most time consuming merge requests and potential causes.
- Authors, labels, or milestones with the longest time to merge, or most changes.

Use productivity analytics to view the following merge request statistics for your groups:

- Amount of time between merge request creation and merge.
- Amount of time between commits, comments, and merge.
- Complexity of changes, like number of lines of code per commit and number of files.

To view merge request data for projects, use [Merge request analytics](../analytics/merge_request_analytics.md).

## View productivity analytics

Prerequisites:

- You must have at least the Reporter role for the group.

1. On the left sidebar, select **Search or go to** and find your group.
1. Select **Analyze > Productivity analytics**.
1. Optional. Filter results:
   1. From the **Projects** dropdown list, select a project.
   1. To filter results by author, milestone, or label,
      select **Filter results** and enter a value.
   1. To adjust the date range:
      - In the **From** field, select a start date.
      - In the **To** field, select an end date.

## View time metrics for merge requests

To view time metrics for merge requests:

1. On the left sidebar, select **Search or go to** and find your group.
1. Select **Analyze > Productivity analytics**.
   Time metrics are displayed on the following charts:
   - **Time to merge**: number of days it took for a merge requests to merge after they were created.
   - **Trendline**: number of merge requests that were merged in a specific time period.
1. Optional. Filter the results:
   - To filter the **Trendline** chart, in the **Time to merge** chart, select a bar.
   - To view a specific merge request, below the charts, from the **List** table select a merge request.

## View commit statistics

To view commit statistics for your group:

1. On the left sidebar, select **Search or go to** and find your group.
1. Select **Analyze > Productivity analytics**.
   Commit statistics are displayed under the **Trendline** scatterplot:
   - The left histogram shows the number of hours between commits, comments, and merges.
   - The right histogram shows the number of commits and changes per merge request.
1. Optional. Filter results:
   - To view different types of commit data, from the dropdown list next to each histogram, select an option.
   - To view a specific merge request, below the charts, from the **List** table select a merge request.