Understanding LinearB Metrics

All Categories

Learning Hub

Misc.

Guides to understanding your LinearB features.

62 articles by 2 authors

12 articles

Metrics

Dashboards and deep-dive reporting for all of your engineering data

5 articles

Metrics Glossary

The Metrics Glossary provides clear definitions and explanations for all metrics tracked in LinearB, including how they are calculated and why they matter

Draft Pull Requests

Draft PRs are a valuable tool for teams to collaborate early in the development process and maintain clear differentiation between work-in-progress and ready-for-review pull requests.

Handling Squash Merges in LinearB

Learn how LinearB ensures accurate coding time metrics when squash merges are used, and how enabling Jira-based coding time can further improve tracking accuracy across your development workflows.

How and When LinearB Counts Commits

LinearB counts commits by tracking repository activity, branch configurations, and optional integrations like Jira. The system ensures accuracy through fallback mechanisms for squash merges, configur…

Indirect Code Contribution 👻

Indirect Code Contribution. Looking at the commits and code that is part of a branch, we distinguish between 2 types of contribution to the branch. Direct contribution - direct commits to the branch.…

Understanding Code Changes

Understanding Code Changes. General. Code changes is a metric that measures the changes that are done in the code base over time. It includes either new code or refactored code and is counted in a nu…

Understanding the Differences Between PR Size and Code Changes in LinearB

Understand the key differences between PR Size and Code Changes in LinearB to accurately measure development effort, track modifications, and optimize your engineering workflows.

What are LinearB Burnout Indicators?

Avoid burnout and cognitive overload by monitoring and balancing your team's workload.

Why does my Cycle Time keep changing?

Cycle Time is a fluid metric: 1. branches change 2. post-iteration change 3.

Work Breakdown Terms

Work Breakdown Terms. Refactor - Changes to legacy code. LinearB considers code "legacy" if it has been in your code-base for over 21 days. Rework - Code that is rewritten or deleted shortly after be…