Label groups Per stage On the record

Require the right labels at each stage in Linear

Stop chasing missing labels before planning and bug reviews. Require Severity before a bug enters In Progress and Root Cause before Done. If either is missing, LineGuard moves the issue back and tells the teammate what to add.

Add to Linear — free See the three rules

Three rules · One team · No card required

Not a workspace admin? Send it to the person who is.

What your team sees

The issue goes back, with a note saying why

No new tool to check and no dashboard to police. The fix happens in Linear, on the issue, from the person who moved it.

ENG-1482 Sam moves a bug to Done with no Root Cause label.
Within seconds LineGuard moves it back to the state it came from.
It leaves a comment in your wording, with the missing group filled in, and records the whole thing.
Sam picks a Root Cause label and moves it to Done again. This time it stays there.

LineGuardjust now

@Sam Okafor this bug was closed without Root Cause. Tag it (Regression, Config, Missing test…) and close it again. It's what the monthly quality review runs on.

Illustration The comment is written from the rule's own template.

The gap

The information you need changes as work progresses

Area belongs at triage. Severity belongs before work starts. Root Cause belongs before the bug closes. A Linear form template can require a label group when an issue is created, but nothing asks again once the issue starts moving.

Missing labels survive status changes

A bug can reach Done without a Root Cause label, leaving someone to chase the answer before the next review.

Each stage needs something different

Ask for everything at creation and Root Cause is a guess, because the fix hasn't happened yet. Each field has to be checked at the step where someone actually knows the answer.

Not every issue needs every label

A feature doesn't have a Severity. The rule has to know it's looking at a bug before it asks.

Where to start

Three rules, on the free plan

These three cover a bug from intake to close, and each one checks one label group at one step.

Leaves Triage

Area is set

Moves back if Area is missing

Require an Area such as Billing, API or Mobile, so the backlog can be filtered by product area before planning.
Bug enters In Progress

Bugs have a Severity

Moves back if a Bug has no Severity

Make the bug's impact explicit before work starts. The requirement applies only to issues labelled Bug.
Bug enters Done

Bugs have a Root Cause

Moves back if a Bug has no Root Cause

Capture the cause while the fix is fresh, so the next bug review doesn't start by reopening old issues.

Choose any three rules on the free plan. Require labels, an assignee, an estimate or a priority wherever your workflow needs them. Upgrade when you need more rules or teams.

The product

Built in a few dropdowns, not a script

Screenshots of the real dashboard, from an example workspace. The entries are seeded, not a customer's results.

Conditional

Required only where it applies

Choose a label group such as Severity. Any label in that group satisfies the requirement. You decide which issues need it and at which stage: here, only bugs, and only once they enter In Progress.

The LineGuard rule builder: trigger 'Issue enters state In Progress'; conditions 'labels contains Type › Bug' AND 'label group Severity is_empty'. — Example workspaceView full size

Audit log

Every catch on the record

See which issues were moved back, what was missing, and which action LineGuard took. Spot recurring gaps without checking issues one by one.

The LineGuard audit log: ENG-1482, ENG-1479, ENG-1491 and other issues, each with the rule that caught it and the revert_state and add_comment actions taken. — Example workspaceView full size

Start with the label your team forgets most

Require it at the stage it matters, and let LineGuard handle the reminder. Free for three rules on one team. No card required.