Merge Request Analytics (STARTER)
Merge Request Analytics helps you understand the efficiency of your code review process, and the productivity of your team.
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.
This feature is designed for development team leaders 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.
The throughput chart shows the number of merge requests merged per month.
Data table displaying a maximum of the 100 most recent merge requests merged for the time period.
Filter the data
Introduced in GitLab 13.4
You can filter the data that is presented on the page based on the following parameters:
To filter results:
- Click on the filter bar.
- Select a parameter to filter by.
- Select a value from the autocompleted results, or enter search text to refine the results.
The Merge Request Analytics feature can be accessed only:
Enable and disable related feature flags
Merge Request Analytics is disabled by default but can be enabled using the following feature flag:
A GitLab administrator can:
Enable this feature by running the following command in a Rails console: