Skip to main content

Quality Metrics

Purpose. Quality Metrics measure code health and review rigor. They help you understand whether pull requests are reviewed effectively, how risky changes may be, and how much rework or refactoring is…

Steven Silverstone
Updated by Steven Silverstone

Purpose

Quality Metrics measure code health and review rigor. They help you understand whether pull requests are reviewed effectively, how risky changes may be, and how much rework or refactoring is occurring over time.

Metrics Included

The following metrics belong to the Quality family:

Each metric definition, calculation formula, normalization logic, and display behavior is documented in the Metrics Glossary.

How These Metrics Work Together

Quality metrics provide signals across three areas:

  • Change risk (for example, PR Size and PR Maturity)
  • Review rigor (for example, Review Depth and PRs merged without review)
  • Code churn and stability (for example, New Code, Refactor, and Rework)

Use these metrics together to distinguish between healthy improvement (refactoring) and instability (rework), and to validate whether review practices match the risk profile of changes.

Dashboards That Use Quality Metrics

Quality metrics appear in:

These dashboards combine Quality metrics with Delivery and Throughput metrics to provide contextual insights.

Quality metrics often correlate with:

  • Delivery Metrics (review time and approval time are affected by review rigor)
  • Throughput Metrics (higher output can increase quality risk if review rigor does not scale)
  • AI Metrics (AI-assisted review and issue identification may affect quality signals)

Configuration Dependencies

Quality metrics rely on:

  • Pull request and review events (reviews, comments, approvals)
  • Accurate PR activity ingestion from the connected Git provider
  • Issue identification sources (when applicable)

Troubleshooting

If Quality metrics appear inconsistent:

  • Validate review events (approvals/comments) are being ingested correctly.
  • Confirm PR activity exists during the selected time range.
  • For issue identification metrics, validate the relevant data source is enabled and syncing.

For detailed troubleshooting guidance, see: Troubleshooting.

How did we do?

Contact