Hi PH 👋 I built LineGuard because of a recurring argument at Product Engineering: our velocity numbers were wrong, and the reason was boring — issues were reaching Done with no estimate on them. Linear has no way to require a field before a status change, so the fix was always "remind people in standup," which works for about a week. LineGuard watches for the change and undoes it, with a comment saying what's missing. Trigger → conditions → action. Nine presets cover the common ones ("No Done without an estimate", "Nothing starts unassigned"), so you're not staring at an empty rule builder. Two honest caveats: — Linear's webhooks fire *after* a change is committed, so nothing can truly block a transition. The issue moves, then bounces back. Everyone in this category works this way; there's no pre-commit hook to use. — Today the actions are revert-and-comment. Auto-setting fields and transition-path rules are next. Pricing is flat per workspace rather than per seat — this is an admin tool, and charging you more for hiring engineers who never open it never made sense to me. Free tier is a real one. Would genuinely like to hear which rule you'd want first. That list is how I've been picking what to build.

LineGuard

Required fields and workflow rules for Linear

Required fields and workflow rules for Linear