Use Project Milestones in Linear
Group project issues into meaningful stages and track each milestone separately. A milestone is a scope checkpoint inside a project, rather than a second project or a release guarantee.
Step-by-step guide
Check access and scope
You need a project with issues and an agreed definition of what each stage demonstrates.
Create the milestone
Open the project details and create a named milestone.
Define exit evidence
Add a description explaining the evidence needed to pass it.
- Worked example: For a new invite flow, use Internal validation, Limited rollout and General availability. Put security checks in Internal validation and customer migration tasks in Limited rollout.
Assign milestone scope
Assign relevant project issues to the milestone. Shift M opens milestone assignment for the issue; check the issue is in the intended project first.
Choose a target date
Set an honest target date if the stage has a known window.
Review critical blockers
Review incomplete scope and update the milestone before communicating progress.
Verify the result
Opening each milestone shows the intended issue set and a reviewer can explain what completion means.
Common mistakes
Avoid the main failure mode
A nearly full progress indicator can hide one critical blocker. Review issue importance as well as issue counts.
Check the handoff edge case
Naming milestones after departments hides the outcome required to finish each stage. Use a decision or readiness condition instead.
Sources and verification
Based on product documentation checked on 2026-10-24. This is a documentation-based guide, not a hands-on benchmark. Features and availability can change.