Using LinearB Insights

All Categories

Learning Hub

A metric turned red. Now what? This hub helps you interpret delivery, quality, and flow signals and choose the right next step, from diagnosis to guardrails.

8 articles by 1 author

How to Address Hanging Review Requests and Long Reviews

Reviews are important "team" task. Reviews affect both quality of code and delivery. Hanging reviews slows down the cycl…

How to Address High Risk Work

High-risk work refers to code changes that are large in size and heavily focused on rework or refactoring. These changes increase the likelihood of introducing defects and should be handled with addi…

Managing Large Pull Requests to Reduce Review Friction and Risk

Learn why large pull requests slow teams down, increase risk, and how LinearB helps you detect, manage, and improve them using AI insights, team workflows, and automation.

Preventing Pull Requests from Being Merged Without Proper Review

Code reviews are a critical safeguard for code quality. Even highly experienced developers can overlook issues after working on the same code for an extended period. A proper review introduces a fres…

Reducing High Pull Request Review Time

It's integral to a continuously developing team to be reviewing code as close to real-time as possible. Here are some ways to reduce review time.

Reducing Pull Request Pickup Time

Continuous improvement depends on how quickly teams respond to pull requests (PRs) and keep the review process moving. High Pickup Time slows delivery, as PRs that remain unreviewed delay the entire…

Troubleshooting: Pull Requests Are Not Showing in LinearB

Having trouble seeing your pull requests in LinearB? This article outlines common reasons why PRs might be missing from metrics, activity views, or alerts.

Understanding and Fixing Unlinked Branches

Unlinked branches are branches your team is actively working on that are not associated with any tracked project issue. When branches are unlinked, LinearB cannot connect the work to planning, progre…