Changes Dashboard
Available in CDviz Cloud
The Changes dashboard ships today in CDviz Cloud. It is built on the same change.* CDEvents as the rest of the stack, so a self-hosted Grafana version can follow — the change lifecycle is also covered from the incident side in the Incidents & Tickets dashboard.
Overview
The Changes dashboard tracks the pull-request / change-request lifecycle across all your connected repositories. It consolidates change events from GitHub, GitLab, or Jira as long as they emit CDEvents, so you can see delivery flow without opening every repo's PR tab.
Key questions answered:
- How many changes are in flight right now — created, in review, merged, abandoned?
- What is our merge throughput, and is it trending up or down?
- What is the cycle time from change creation to merge?
- Which changes have been open the longest and need attention?
Dashboard Panels
Change Summary
An at-a-glance stat row: changes created, in review, merged, and abandoned in the selected time window, plus median cycle time from change.created to change.merged.
Merge Throughput
Merged changes over time, grouped by day or week — the delivery-flow signal that tells you whether work is actually shipping, and lets you spot slowdowns before they show up as missed sprint goals.
Open & Oldest Changes
A scrollable list of currently open changes, sorted oldest first, so stale pull requests that have stalled in review surface at the top instead of rotting unnoticed.
CDEvents Requirements
| Event type | Used by |
|---|---|
change.created | Change Summary, Cycle Time, Open Changes |
change.reviewed | In-review count |
change.merged | Change Summary, Merge Throughput, Cycle Time |
change.abandoned | Change Summary |
NOTE
Panels show no data — not zero — when the required event types have not been emitted. If your tools do not yet emit CDEvents natively, configure the CDviz Collector to translate webhook payloads using transformer rules.
Connecting Your Tools
Use the corresponding CDviz Collector integration or a webhook transformer to emit change.created, change.reviewed, change.merged, and change.abandoned CDEvents from pull-request or issue state transitions in GitHub, GitLab, or Jira.
See the Transformer Rules documentation for mapping examples.
Technical Notes
Cycle time is computed as change.merged.timestamp − change.created.timestamp. Changes that are abandoned (never merged) are excluded from that calculation.