Completed Project Review in Linear
Keep the completed project and its decision history rather than deleting it. Use project status to distinguish finished work; issue archiving is a separate cleanup operation.
Step-by-step guide
Check access and scope
Access to the project and agreement from its lead are required. Check whether unfinished issues still need an active home.
Review the overview
Open the project overview and record its current status, lead and target date.
Move unfinished work
Review unresolved issues and move continuing work into a follow-up project.
- Worked example: For a completed invitation-flow release, retain the spec and rollout notes. Move an outstanding domain-validation bug to the maintenance project, with a link to the original release.
Record the final update
Write a final project update with shipped scope, exclusions and links to results.
Mark the project complete
Change the project to the appropriate completed project status.
Filter active projects
Use project filters to exclude completed work from active planning views. Project archiving is automatic: closed status, inactivity and issue eligibility affect when the project enters the team archive; marking complete is not a manual archive button.
Verify the result
Find the finished project again, open its documents, and confirm the active-project view excludes it.
Common mistakes
Avoid the main failure mode
Deleting a project is not the same as removing it from an active view; deletion starts a limited recovery period.
Check the handoff edge case
Leaving unfinished issues in a completed project makes the retained history look like an active delivery commitment. Move continuing work deliberately.
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.