Atlassian's Compass is moving to DX. If you want delivery metrics inside your Confluence pages, GitHub Links for Confluence offers a lightweight, in-context option - live DORA-style metrics rendered directly on any page, next to your narrative, runbooks, or team documentation.
Compass is moving to DX - Atlassian announcement
What is available
Three macros cover the core delivery signals:
|
Macro |
What it measures |
|---|---|
|
How long PRs take 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 metrics - not a full DORA implementation. Change Failure Rate (CFR) and Mean Time to Recovery (MTTR) are not included in v1.
Metrics are always team-level only - never per-developer. The app stores no code or PR data, and reporting is included in your standard subscription with no additional setup beyond your existing GitHub connection.
Who this is for
-
Engineering managers or team leads who tracked delivery signals in Compass and want continuity inside Confluence
-
Teams wanting DORA-style signals on a page alongside their engineering documentation
-
Stakeholders wanting live metrics next to narrative in QBRs, roadmap pages, or team homepages
Set up a basic delivery view
-
Open or create a Confluence page (e.g. your team homepage or a dedicated metrics page).
-
Type
/PR Throughputand configure with your repositories and date range. -
Type
/PR Cycle Timewith the same scope. -
Type
/Review Latencywith the same scope. -
Publish - the macros render live on each page load.
Keep date ranges consistent across macros so the metrics are directly comparable.
Going further
-
Use case: Engineering QBR / stakeholder page with live delivery metrics - a worked example
-
How metrics are calculated - definitions, period handling, and limitations
-
Reporting Macros - full configuration reference for each macro
Updated: