We're excited to launch Engineering Reporting - team-level GitHub delivery metrics that render live on your Confluence pages.
What's new
Three new macros are now available in GitHub Links for Confluence:
|
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 |
Highlights
-
DORA-style delivery metrics, in context. PR Cycle Time, PR Throughput, and Review Latency render live on any Confluence page alongside your documentation and narrative. (CFR and MTTR are not in v1.)
-
Computed live from GitHub. Metrics are fetched from the GitHub API on each page load - always current, never a screenshot.
-
We store no code or PR data. Only computed aggregates are cached briefly. Your source code and PR contents never leave GitHub.
-
No new setup required. The macros reuse your existing GitHub App connection. No new GitHub scopes or permissions needed to start.
-
Included at your standard subscription. No separate pricing.
-
A lightweight in-context option as Compass moves to DX. If your team tracked delivery signals in Compass, these macros offer continuity inside Confluence. Atlassian announcement
Get started
-
Open any Confluence page in edit mode.
-
Type
/PR Cycle Time(or/PR Throughputor/Review Latency), or use the + Insert menu. -
Select your repositories and a date range.
-
Save and publish.
Full documentation: Reporting Macros
Released: