Review Latency report
The Review Latency macro measures how long pull requests wait before receiving their first review. High review latency is a common bottleneck that slows overall delivery. Data is fetched live from GitHub.
Adding the macro to a page
Open a Confluence page in edit mode.
Type
/Review Latencyor click + and search for Review Latency (GitHub).Configure the options and click Save.
Configuration options
Option | Description |
|---|---|
Repositories (required) | Select one or more repositories. Type to search within your connected organisation. |
Labels | Only include PRs with at least one of these labels. |
Assignees | Only include PRs assigned to these users. |
Date range | Last 14 days, Last 30 days (default), or Last 90 days. |
Display | Full (KPI + chart) or Compact (KPI tile). |
Compare to previous period | Compare to the prior equivalent period. Enabled by default. |
Exclude bot / dependabot PRs | Filter out bot-authored PRs. Enabled by default. |
Title (optional) | Custom heading. Defaults to Review Latency - {selected repositories}. |
What is measured
Review latency is calculated as the time from PR opened to the first review comment or approval. The macro shows the average time to first review across matching PRs, a trend indicator vs. the previous period, and a chart showing review latency over time (Full display only).
Related pages
PR Cycle Time report - average time from PR opened to merged
PR Throughput report - how many PRs your team is merging over time
Preparing sprint retrospectives - using the reporting macros alongside PR and issue data in retro pages
Updated: