How to Set Up a Deployment Checklist in Linear
Linear does not have a native checklist feature, but its issue templates, sub-issues, and Projects provide the building blocks for a structured deployment checklist workflow. The advantage of putting your deployment checklist in Linear over a standalone document is that checklist completion is tracked alongside the engineering tickets being deployed.
This guide covers how to build a deployment checklist system in Linear, how to use issue templates for different release types, and how to link the checklist to the tickets in the release.
Step-by-step guide
Create a Deployment Checklist issue template
In Linear, go to Settings > Templates > New Template for your engineering team. Name it "Deployment Checklist — Standard Release." In the description, add your checklist phases as markdown headers with sub-tasks listed under each. Linear supports markdown in issue descriptions, so you can use checkboxes (- [ ] Step name) that engineers click to complete during the deploy.
Set up a Release Project per deployment
For each significant release, create a Linear Project named by release identifier: "Release 2.4.1 — Aug 28." Create the deployment checklist issue from your template inside this Project. Link all tickets being shipped in this release to the Project as well. This creates a single Project that contains both the "what are we shipping" (tickets) and the "how are we shipping it" (checklist).
Use sub-issues for checklist phases
Create the deployment checklist parent issue and then add sub-issues for each phase: "Pre-deployment verification," "Deployment execution," "Post-deployment validation." Assign each sub-issue to the responsible engineer. Linear's project view shows sub-issue completion as a progress bar on the parent issue, giving release managers a real-time view of checklist progress without reading every sub-issue.
Add a Release label and filter for release tracking
Create a Linear label "release-checklist" and apply it to all deployment checklist issues. Create a saved filter in your team view for issues with this label. This gives engineering managers a dedicated view of all deployments — past and upcoming — without mixing them with feature work. Sort by Created date to see deployment history.
Connect checklist to shipped tickets
In the deployment checklist issue description, add a section "Tickets in this release" with links to all the Linear issues being deployed. Post-deployment, when you mark the checklist complete, the linked issues provide the full context of what changed. During incidents, this connection lets you identify which specific ticket introduced a regression without scanning the full commit history.
Common mistakes
Using a single shared checklist issue instead of one per release
A deployment checklist that is never reset — where engineers uncheck and re-check the same issue — provides no audit trail. Create a fresh issue from the template for every release. The historical checklist issues serve as evidence of what was verified for each deployment, which is essential during postmortems.
Checklist without a blocking relationship to the release
If the deployment checklist issue is created in Linear but has no relationship to the release process, engineers will skip it under time pressure. Make the checklist issue a blocker for the "deployment complete" milestone ticket. Linear's dependency system can enforce that the checklist is marked complete before the release is closed.
No distinction between pre- and post-deployment steps
Mixing pre-deployment verification (backups checked, staging tested) with post-deployment validation (production smoke test, metric baseline) into one flat checklist causes confusion during a live deployment. Separate phases either as sub-issues or as clearly marked sections in the issue description.
Tips
Use Linear's cycle integration to include the deployment checklist issue in the same Cycle as the tickets it covers — this keeps release execution visible in sprint tracking
Add estimated duration to each checklist phase in the sub-issue title: "Pre-deployment verification (~20 min)" — this helps release engineers plan deployment windows
Create separate templates for different risk levels (standard, hotfix, breaking-change) rather than a single universal template so checklist length matches release risk
How Vantage helps
A Linear deployment checklist tracks the operational release process. Vantage connects the release to the product: each ticket in the release traces back to PRD requirements, so the post-deployment smoke test can be structured around verifying the acceptance criteria that were committed to. Release engineers see what product outcomes should be confirmed, not just which services were deployed.