Skip to main content

Understanding LinearB Metrics

Guides to understanding your LinearB features.

author avatar author avatar
22 articles by 2 authors
5 articles

Video Tutorials

Enjoy our video guides!
10 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/WIP Pull Requests. Currently Draft PRs are supported in GitHub and GitLab. Azure repos does not currently report via their API the date-time of when a PR made live and BitBucket does not have t…

How does LinearB handle squash merges?

What is Git Squash? Git squash is a feature that allows developers to merge multiple sequential commits. The process involves choosing a base commit and merging all the changes from the sequential co…

How is Cycle Time Calculated?

How is Cycle Time Calculated. Cycle time calculates the average time it takes for engineering tasks to go through the different phases of the software delivery process, from the first code commit to…

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 Releases

LinearB tracks releases and incorporates release counts into several key metrics, such as Deployments and Deploy Frequency.

What are LinearB Burnout Indicators?

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

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…

Contact