Metrics Dashboards & Reports in LinearB – LinearB Support

Use the Metrics area in LinearB to track DORA outcomes, understand delivery and quality trends, inspect outliers, and build custom investment-style reports for your teams and repos.

TL;DR – What you can do here

Use default dashboards (Delivery, Quality, Throughput, DORA) to monitor core engineering health.
Filter by time, teams, contributors, repos, and PR labels to focus on the work that matters.
Drill into outliers with Metrics Inspection to see which teams, services, or repos drive changes.
Use repository-level metrics to compare performance across codebases.
Build custom dashboards to track investment, PM metrics, and reported events over time.
Share & export dashboards via links, CSV, PNG, or the LinearB Measurements API.

Getting started

Where to find Metrics

From the LinearB app, go to the Metrics section in the left navigation. You’ll see default dashboards as tabs and any custom dashboards your team has created.

Date ranges & plans

Each dashboard includes a date picker in the upper-right corner:

Essentials – up to 6 months of historical data.
Enterprise – up to 3 years of historical data.

All charts and tables on the page respect the selected date range.

Filters

Every metrics dashboard shares a common filter bar so you can focus on specific slices of work:

Teams – select one or more teams.
Members – filter down to specific contributors.
People / Contributors – control which people are included in calculations.
Repositories – focus on particular repos or services.
PR labels – include / exclude work by PR label (details below).

Filters apply consistently across charts in the selected dashboard and are included when you share or export a dashboard.

Default metrics dashboards

LinearB ships with several pre-built dashboards focused on different aspects of delivery. You can customize filters and date ranges, but the dashboards themselves are always available.

Delivery dashboard

The Delivery dashboard helps you understand how quickly work is moving through your system. Typical metrics include:

Cycle time trends and breakdown (Coding, Pickup, Review, Deploy).
Throughput (PRs merged, branches completed).
Work in progress and batch size trends.

Use this view to identify bottlenecks in handoffs, review delays, and changes in delivery speed.

Quality dashboard

The Quality dashboard tracks stability and failure patterns over time, including:

Change Failure Rate (CFR) – % of deployments that lead to incidents or rollbacks.
Mean Time to Restore (MTTR) – how long it takes to recover from failures.
Incident and rollback activity where configured.

Use this dashboard to understand how changes in process or release cadence affect production reliability.

Throughput dashboard

The Throughput dashboard focuses on volume and consistency of delivery, typically including:

PRs merged over time.
Completed branches or stories.
Deployments to production and other stages.

Use this to track output across teams and see how throughput changes over weeks, sprints, or quarters.

DORA Metrics dashboard

The DORA Metrics dashboard shows the four classic DORA metrics plus supporting context, helping you connect day-to-day activity to high-level engineering outcomes.

Metrics included

Deployment Frequency – how often code is successfully deployed.
Lead Time for Changes – how long it takes from code commit (or PR creation) to production.
Mean Time to Restore (MTTR) – how quickly you recover from incidents.
Change Failure Rate (CFR) – percentage of releases that result in failures.

How to use it

Apply Team and Repository filters to compare DORA outcomes across groups.
Use date ranges to see improvement over quarters or before/after major initiatives.
Click into charts to open Metrics Inspection and see which repos or teams drive a trend.

You can also include DORA metrics in custom dashboards alongside other widgets when building investment or leadership views.

Metrics Inspection

Use Metrics Inspection when you want to understand why a metric changed, not just that it changed.

Opening Metrics Inspection

On a supported chart, click the Inspect or Metrics Inspection option.
In some views, you can also click a data point (for example, a specific week) and choose to inspect it.

What you’ll see

A focused view of the metric for the selected time range.
Breakdowns by team, repository, or project (depending on the metric).
A table listing the entities (teams/repos/projects) with their contribution to the selected metric.

Typical workflows

Cycle time spike: Inspect the point, then see which repos or teams had the biggest increases.
Drop in deploys: Inspect deployment frequency to find which services slowed down and why.
CFR increase: Inspect change failure rate to see which repos are contributing failed releases.

From Metrics Inspection you can often click through to Activity, repository views, or specific items (PRs, releases, incidents) to continue your investigation.

Repository-level metrics

Repository-level metrics help you understand how individual repos are performing, independent of team structure.

Why use repo-level views

Compare cycle time and throughput across services or codebases.
Identify repos with higher CFR or slower review cycles.
Spot where most work is happening so you can align ownership and staffing.

How to use them

Open a relevant dashboard (for example Delivery, Quality, DORA).
Set the Repository filter to one or more repos to focus your view.
Use Metrics Inspection to see which repos contribute most to a trend.

Repository-level filters work just like team and member filters and are included in shared links and exports.

Custom metrics dashboards & investment reports

Use custom dashboards when you want to build investment-style reports or leadership views that combine DORA, delivery, quality, and PM metrics in one place.

Create a custom dashboard

In the Metrics area, click + New dashboard (or the equivalent option for custom boards).
Give the dashboard a name (for example, “Investment – Q1 Platform Work”).
Click Add chart to add widgets for the KPIs you care about.

Widget types

Depending on your setup and plan, you can add:

Standard metric widgets – cycle time, throughput, PRs merged, CFR, MTTR, etc.
PM metrics widgets – issue counts or story points from tools like Jira or Azure Boards (when connected).
Reported metrics widgets – metrics you send via the Report Event API (for example, incidents, business KPIs).

Configuring PM & reported metrics widgets

For PM / reported metrics widgets you’ll typically choose:

Metric type – issue count or story points.
Scope – which projects, boards, or filters to use.
Issue types – for example, story, bug, task (when supported by your PM tool).
State(s) – single state (e.g., “Done”) or transitions between two states (e.g., “In Progress → Done”).

Each widget has a settings menu (gear icon) where you can adjust filters, rename the chart, or remove it from the dashboard.

Selecting multiple teams

Most dashboards support selecting multiple teams at once, letting you compare performance and investment across groups.

How to select multiple teams

Open a metrics dashboard.
Click the Teams filter.
Select one or more teams from the list.

All metrics on the page are recalculated based on:

The teams you selected.
Any additional filters (members, repos, PR labels).
The current date range.

This is useful when you want a single “portfolio” dashboard across multiple delivery groups or squads.

PR label filters in metrics reports

PR label filters let you slice metrics by how work is categorized in your git provider (for example, “feature”, “bugfix”, “chore”, or any custom labels your teams use).

How the PR label filter works

Open a metrics dashboard that supports PR labels (for example, Delivery, DORA, Throughput).
Use the PR labels filter to:
- Include only PRs with specific labels.
- Exclude certain labels (for example, “dependencies” or “docs-only”).

Only PRs that match the label filter are included in calculations for cycle time, throughput, DORA metrics, and related charts on that dashboard.

Share a dashboard link

Click Copy Link to Dashboard (or the share icon) on any metrics dashboard.
The link includes the current filters and date range.
Send the link via Slack, email, or any other channel.

Recipients must have the appropriate LinearB permissions to view the dashboard. Private dashboards are only visible to users who have access.

Export as CSV

Click Export as CSV on a supported dashboard.
Each metric widget becomes a column in the CSV.
Each row represents a time bucket (e.g., daily/weekly) for the selected date range.

CSV export availability:

Available for pre-defined dashboards:
- DORA Metrics
- Delivery Metrics
- Quality Metrics
- Throughput Metrics
Available for personal/custom dashboards built with standard metric widgets.
Not available for Custom PM Metrics reports.

Export as PNG

Click Export as PNG to generate an image of the dashboard.
Use this in slides, documents, or async status updates.

Metrics API

For programmatic access, use the LinearB Measurements API to pull metrics into your own data warehouse or BI tools. You’ll need an API token generated from the LinearB Company Settings.

Best practices

Anchor on DORA: Start from the DORA dashboard to understand outcomes, then drill into Delivery, Quality, and Throughput to find root causes.
Use Metrics Inspection for spikes: When you see a change in a chart, inspect it immediately to see which teams, repos, or projects shifted.
Standardize labels: Align PR labels across teams so label-based filters give you clean, reliable slices of work.
Build a few canonical dashboards: Create shared “Leadership” or “Investment” dashboards instead of many one-off views.
Share links instead of screenshots when possible: Links preserve filters and date ranges and stay current as data updates.