75 lines
3.2 KiB
Markdown
75 lines
3.2 KiB
Markdown
---
|
|
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: Analytics
|
|
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/#designated-technical-writers
|
|
---
|
|
|
|
# Merge Request Analytics **(STARTER)**
|
|
|
|
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/229045) in [GitLab Starter](https://about.gitlab.com/pricing/) 13.3.
|
|
|
|
Merge Request Analytics helps you understand the efficiency of your code review process, and the productivity of your team.
|
|
|
|
## Overview
|
|
|
|
Merge Request Analytics displays information that will help you evaluate the efficiency and productivity of your merge request process.
|
|
|
|
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.
|
|
|
|
To access Merge Request Analytics, from your project's menu, go to **Analytics > Merge Request**.
|
|
|
|
## Use cases
|
|
|
|
This feature is designed for [development team leaders](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#delaney-development-team-lead)
|
|
and others who want to understand broad patterns in code review and productivity.
|
|
|
|
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.
|
|
|
|
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.
|
|
|
|
## Visualizations and data
|
|
|
|
The following visualizations and data are available, representing all merge requests that were merged in the past 12 months.
|
|
|
|
### Throughput chart
|
|
|
|
The throughput chart shows the number of merge requests merged per month.
|
|
|
|
|
|
|
|
### Throughput table
|
|
|
|
Data table displaying a maximum of the 100 most recent merge requests merged for the time period.
|
|
|
|
|
|
|
|
## Filter the data
|
|
|
|
> [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
|
|
- Assignees
|
|
- Labels
|
|
- Milestones
|
|
|
|
To filter results:
|
|
|
|
1. Click on 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.
|
|
|
|
## Permissions
|
|
|
|
The **Merge Request Analytics** feature can be accessed only:
|
|
|
|
- On [Starter](https://about.gitlab.com/pricing/) and above.
|
|
- By users with [Reporter access](../permissions.md) and above.
|