Export Project Issues from Linear
Filter issues to the project and export that view as CSV. A row export supports analysis, but it is not a full-fidelity project backup with every linked document and conversation.
Step-by-step guide
Check access and scope
Check project access and export role. Guests cannot export issues; view exports have different limits from authorized workspace exports.
Clear unrelated filters
Open a project issue view and clear unrelated filters.
Review the defined CSV fields
Issue CSV exports use a documented field set, not the columns displayed in your view. Remove unwanted spreadsheet columns after downloading a copy.
- Worked example: Keep ID, Title, Status, Assignee, Estimate and Project Milestone for a delivery review. Maintain a separate index of specifications and other linked resources.
Export the view
From the project issue view, use Export issues as CSV in the project menu or command menu. Count the intended issues first and check the role-specific limit described below.
Inspect sample rows
Inspect the file for scope, row count, dates and empty fields.
Record snapshot context
Store the snapshot with export time, project link and review purpose.
Verify the result
Reconcile the exported row count with the intended issue set, then compare representative rows against Linear, including deliberately included completed or archived work.
Common mistakes
Avoid the main failure mode
CSV data is a snapshot. Editing the spreadsheet does not automatically update Linear or preserve a change history.
Check the handoff edge case
Exporting a filtered subset without recording the filter makes later comparisons misleading. Include the scope and snapshot time.
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.