PR Throughput report
The PR Throughput macro shows how many pull requests your team is merging over time, and optionally compares that to how many new PRs are being opened. Data is fetched live from GitHub.
Adding the macro to a page
Open a Confluence page in edit mode.
Type
/PR Throughputor click + and search for PR Throughput (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 count PRs with at least one of these labels. Leave empty for all PRs. |
Assignees | Only count PRs assigned to these users. Leave empty for everyone. |
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 merged PR count to the prior equivalent period. Enabled by default. |
Exclude bot / dependabot PRs | Filter out bot-authored PRs. Enabled by default. |
Show opened PRs alongside merged | When enabled (default), the chart shows both merged and opened PR counts side by side, making it easy to see whether work is accumulating or being cleared. |
Title (optional) | Custom heading. Defaults to PR Throughput - {selected repositories}. |
What is measured
Merged PRs - number of PRs merged in the selected period, with period-over-period comparison
Opened PRs (optional) - number of new PRs opened in the same period, shown alongside merged to indicate backlog growth or reduction
A chart visualising the trend over time (Full display only)
Related pages
PR Cycle Time report - average time from PR opened to merged
Review Latency report - how long PRs wait before receiving their first review
Preparing sprint retrospectives - using the reporting macros alongside PR and issue data in retro pages
Updated: