Move Issues Between Teams in Linear
Move the existing issue to the receiving team and then audit fields that depend on team configuration. The issue gets a new identifier, while old links redirect.
Step-by-step guide
Check access and scope
Both teams must be in the same workspace and you need access. Agree on destination ownership and whether the current project includes that team.
Capture existing fields
Capture the current issue key, project, labels, estimate and cycle.
Confirm receiving access
Confirm the destination team can access the necessary context.
- Worked example: Move an invitation bug from Support to Identity. Add Identity to its shared project first if appropriate; reapply the destination label taxonomy instead of assuming Support labels survive.
Move a sample issue
Use the issue move-team action for one issue before attempting a bulk move. For one issue, Cmd/Ctrl Shift M opens the move-team action; validate the result before selecting many issues.
Audit mapped properties
Map the status and inspect project, cycle, labels and assignee after moving.
Confirm the handoff
Notify the receiving owner and update text references where clarity matters.
Verify the result
The old URL redirects to the moved issue and the receiving team sees the correct scope and owner.
Common mistakes
Avoid the main failure mode
Undo does not guarantee every label, subscription or access-related assignment returns exactly as before. Avoid blind bulk moves.
Check the handoff edge case
Moving many issues before checking one representative record can multiply field-mapping errors. Validate a single move first.
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.