...
Standard Version Control Summary metric shows overall information about merge requests request states. But what if you want to track this information on a regular basis to be able to follow the trends? In such cases, you may want to create a custom metric specifically for your needs. Here is an example of how to do it.
Description
This metric is based on GIT data.
Metric collects all pull requests submitted in a specific month & break breaks them down to into 3 buckets (Accepted, In Review & Rejected)
...
Configuration
We have 1 variables variable in the code of this metric:
...
How to interpret this metric & next steps
Big A big number of rejected merge requests can indicate issues with risky or too complicated changes, poor code quality, etc. The trend will help you to understand whether this is a one-time or usual case.
If there are a lot of repositories, branches, it's a good idea to add additional filtering or/and create some more of such metrics for specific repositories.
It would be a good idea to convert number of merge requests to %.
As a next step, it would be good to map rejected merge requests with people to see if there are correlations - e.g. majority of rejected merge requests were submitted by specific developer.
...