Acceptance Criteria Template for Linear (2026)
Linear keeps issue descriptions lean, so acceptance criteria need to be clear and concise. This template shows how to structure criteria in Linear using markdown checklists and sub-issues for granular tracking.
Consistent acceptance criteria in Linear reduce misunderstandings and speed up code review.
Template sections
4 sections covering the complete acceptance criteria workflow.
Inline Checklist
Add acceptance criteria as a markdown task list in the issue description. Linear renders checkboxes natively. Engineers check off criteria as they implement. Reviewers verify during code review. This is the simplest approach for most teams.
Sub-Issue Approach
For complex features, create each acceptance criterion as a sub-issue. This allows individual assignment, separate status tracking, and linking to specific PRs. Sub-issues roll up to the parent issue progress bar.
Given/When/Then
Use Gherkin syntax in the description for behavior-driven criteria. Linear markdown supports code blocks for formatting scenarios. This format is especially useful when criteria need to map directly to automated tests.
Labels for QA
Create Linear labels: "Needs QA," "QA Passed," "QA Failed." Add a workflow automation: when all sub-issues are complete, apply the "Needs QA" label. QA reviews criteria and updates the label, creating a lightweight sign-off process.
Copy-paste template
## Issue Description [User story or feature context] ### Acceptance Criteria - [ ] [Criterion 1: happy path] - [ ] [Criterion 2: validation] - [ ] [Criterion 3: edge case] - [ ] [Criterion 4: performance] ### Scenarios (for complex criteria) ``` Given [precondition] When [action] Then [result] ``` ## Linear Setup - Labels: Needs QA, QA Passed - Sub-issues: [Create if >5 criteria]
Frequently asked questions
Generate instead of filling in templates
Connect your tools, and Vantage generates the content using real product data. Free to start.
Free to start. No credit card required.