Engineering Reporting adds three macros that render team-level GitHub delivery metrics live on a Confluence page. Unlike the GitHub Links macro - which embeds a specific GitHub entity - the Reporting Macros aggregate data across repositories and display KPI tiles and trend charts.
Each macro can be added to any Confluence page: sprint retrospectives, team dashboards, engineering wikis, or stakeholder QBR pages.
|
Macro |
What it measures |
|---|---|
|
How long PRs take to move through your team's workflow - from opened to merged |
|
|
How many PRs your team completes over a period |
|
|
How long PRs wait before receiving their first review |
These are DORA-style delivery metrics - not a full DORA implementation. Change Failure Rate (CFR) and Mean Time to Recovery (MTTR) are not included in v1.
Privacy: Metrics are always team-level - never per-developer. The app stores no code or PR data. See What we store (reporting) for details.
Going further
|
Page |
What it covers |
|---|---|
|
Definitions, period handling, data sourcing, and v1 limitations |
|
|
Full privacy and data storage detail for reporting |
|
|
Using reporting as a lightweight alternative as Compass moves to DX |
|
|
Use case: Engineering QBR / Stakeholder page with live delivery metrics |
A worked example of a live QBR page |
Updated: