Skip to main content

How Metrics Work

Learn how LinearB metrics are calculated and how commits, pull requests, and workflow activity affect dashboard results.

Steven Silverstone
7 articles by 1 author

Exclude Non-Working Days from Cycle Time

LinearB provides the option to exclude weekends from cycle time calculations

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

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 number of code lines that were…

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.

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 25 days. Rework - Code that is rewritten or deleted shortly after be…

Contact