linear-issues

Standardize Linear issue creation by using a template-driven workflow that enforces strict data integrity. This approach separates the original request from the final resolution, ensuring consistent documentation for bugs, features, and infrastructure tasks.

Enforce verification evidence during Linear issue closure by implementing lifecycle management rules. This prevents premature description edits and requires validation proof before transitioning tickets from open to closed, maintaining high-quality engineering documentation.

Structure a Linear bug report by using a canonical authoring template that formats the issue body with required sections like Repro and Root Cause. This ensures the TL;DR remains clear and preserves the original issue intent.

Track research and infrastructure tasks in Linear using a structured workflow that standardizes documentation across all engineering work. This facilitates consistent ticket updates and ensures all actionable context is preserved throughout the lifecycle.

Separating the original ask from the resolution in Linear issue templates preserves the initial issue intent within the TL;DR. This prevents context loss during updates and maintains strict data integrity throughout the ticket lifecycle.