> Source: https://www.gitdash.info/docs/metrics-pr-cycle · GitDash v4.7.1

# PR Cycle Time Breakdown

Lead Time is split into four sequential phases. Each phase reveals a different bottleneck. The proportional bar on the repo overview page shows how much of total lead time each phase consumes.

| Phase | Start → End | What a long value means |
| --- | --- | --- |
| Time to Open | Oldest commit on the branch → PR created | Developers are sitting on local branches too long before opening a PR. Encourages smaller, more frequent PRs. |
| Pickup Time | PR created → first review comment or approval | Reviewers are slow to start. May indicate too many concurrent open PRs, unclear ownership, or team capacity issues. |
| Review Time | First review → PR approved | Reviews require many back-and-forth cycles. May indicate large/complex PRs, unclear requirements, or strict standards. |
| Merge Time | PR approved → merged | CI is slow, there is a merge queue backlog, or developers do not merge promptly after approval. |

The stacked bar on the Repo Overview page colours each phase proportionally. Hover any segment to see its raw duration and percentage of total lead time.