| --- |
| title: "PR Pickup Time" |
| description: > |
| PR Pickup Time |
| sidebar_position: 16 |
| --- |
| |
| ## What is this metric? |
| The time it takes from when a PR is issued until the first comment is added to that PR. |
| |
| ## Why is it important? |
| PR Pickup Time shows how engaged your team is in collaborative work by identifying the delay in picking up PRs. |
| |
| ## Which dashboard(s) does it exist in? |
| - [Engineering Throughput and Cycle Time](../../../livedemo/EngineeringLeads/EngineeringThroughputAndCycleTime) |
| - [Engineering Throughput and Cycle Time - Team View](../../../livedemo/EngineeringLeads/EngineeringThroughputAndCycleTimeTeamView) |
| |
| |
| ## How is it calculated? |
| <b>Data Sources Required</b> |
| |
| This metric relies on PRs/MRs collected from GitHub, GitLab, BitBucket, Gitee or other code review tools. |
| |
| <b>Data Transformation Required</b> |
| |
| N/A |
| |
| <b>SQL Queries</b> |
| |
| The following SQL shows how to find the `pickup time` of a specific PR. DevLake pre-calculates the metric and stores it in table.pull_requests. |
| |
| ``` |
| SELECT |
| review_lag/60 as 'PR Pickup Time(h)' |
| FROM |
| pull_requests |
| ``` |
| |
| |
| If you want to measure the monthly trend of `PR pickup time` in the screenshot below, please run the following SQL in Grafana. |
| |
|  |
| |
| ``` |
| SELECT |
| DATE_ADD(date(created_date), INTERVAL -DAY(date(created_date))+1 DAY) as time, |
| avg(review_lag)/60 as 'PR Pickup Time(h)' |
| FROM pull_requests |
| GROUP BY 1 |
| ORDER BY 1 |
| ``` |
| |
| |
| ## How to improve? |
| 1. Use DevLake's dashboard to monitor your delivery progress; |
| 2. Have a habit to check for hanging PRs regularly; |
| 3. Set up alerts for your communication tools (e.g. Slack, Lark) when new PRs are issued. |
