LineGuard

What it does

Linear will not stop an issue moving to Done with no estimate, no owner, and no link to a project. So half the issues in a finished cycle are missing the fields the cycle report is built from, and the velocity number that comes out of it is guesswork.

LineGuard watches the workspace, reverts the changes that break a rule, explains the revert on the issue, and keeps the record. It is built for the person who has to answer for the numbers — the engineering manager, the delivery lead, the founder reading a board they did not fill in themselves.

How it works

You write a rule — a required field, a valid transition, a condition a status must satisfy. LineGuard watches the workspace through Linear’s API. When a change breaks the rule, it reverts the change, comments on the issue with the reason, and records the enforcement.

• Required fields on any status, including Done.
• Transition rules that block invalid status changes.
• An audit record of every enforcement, with the reason.
• Admin-gated: only workspace admins can change the rules.

Who it is for

Teams whose Linear data feeds a report someone has to defend — cycle reviews, forecasts, board updates. If nobody reads your velocity number, you do not need this.

Access and data

LineGuard installs through Linear’s OAuth flow and holds only the workspace data it needs to evaluate rules and keep the audit record. What that covers exactly, and how to remove it, is set out in LineGuard’s privacy policy. Issue titles and descriptions are evaluated in memory and never stored. Uninstalling from Linear invalidates our OAuth tokens immediately, and the workspace record is deleted within 30 days.

Built for Linear. Installs through Linear OAuth; admin-gated by design.