Skip to main content
Version: Next

PR Cycle Time

What is this metric?

PR Cycle Time is the sum of PR Coding Time, PR Time-to-Merge and PR Deploy Time. It is the total time from the first commit to when the PR is deployed.

The reason why we use PR Time-to-Merge rather than PR Pickup Time + PR Review Time is that a merged PR may not have any review. In this case, PR Pickup Time and PR Review Time will be NULL, while PR Time-to-Merge is not.

Why is it important?

PR Cycle Time indicates the overall velocity of the delivery progress in terms of PR.

Which dashboard(s) does it exist in?

How is it calculated?

You can define deployment based on your actual practice. For a full list of deployment's definitions that DevLake support, please refer to Deployment Frequency.

Data Sources Required

This metric relies on PRs/MRs collected from GitHub, GitLab, BitBucket, Gitee or other code review tools.

Data Transformation Required


SQL Queries

The following SQL shows how to find the cycle time of a specific PR. DevLake pre-calculates the metric and stores it in table.project_pr_metrics.

pr_cycle_time/60 as 'PR Cycle Time(h)'

If you want to measure the monthly trend of PR cycle time in the screenshot below, please run the following SQL in Grafana.

DATE_ADD(date(pr.created_date), INTERVAL -DAY(date(pr.created_date))+1 DAY) as time,
avg(ppm.pr_cycle_time)/60 as 'PR Cycle Time(h)'
pull_requests pr
JOIN project_pr_metrics ppm ON =

How to improve?

  1. Divide coding tasks into workable and manageable pieces;
  2. Use DevLake's dashboards to monitor your delivery progress;
  3. Have a habit to check for hanging PRs regularly;
  4. Set up alerts for your communication tools (e.g. Slack, Lark) when new PRs are issued;
  5. Use automated tests for the initial work;
  6. Reduce PR size;
  7. Analyze the causes for long reviews.