Move Issues Between Teams
Preview and confirm cross-Team Issue moves with status, label, key, assignee, and privacy behavior.
Cross-Team moves let an authorized user move one or more Issues from their current Teams into one destination Team while preserving Issue ids, continuous history, and old-key resolution.
Open an active Issue or use an Issue table to select editable Issues, then choose the move action. A selection may contain Issues from different source Teams; Integrity applies one preview and one all-or-nothing move.
Preview the move
After you choose the destination Team, Integrity shows a preview before anything changes. The preview can include:
- The current and destination Issue keys.
- The destination Team and visibility context.
- Status translation into the destination Team workflow.
- Labels that will be kept, translated, or dropped.
- Assignees who will be cleared because they cannot access the destination Team.
- Whether the move applies only to the selected Issues or also to their subtrees.
- The total number of Issues that will change after duplicate selections, overlapping subtrees, and Issues already in the destination Team are resolved.
No Issue is moved until you confirm the preview.
One move can affect up to 200 Issues after duplicate selections and subtree descendants are resolved. Issues already in the destination Team are unchanged and are not counted as moved. If the preview exceeds that boundary, narrow the selection or choose Issue-only scope before confirming.
The confirmation is atomic: either every previewed Issue moves with its mapped properties and history, or none do. If another change makes the preview stale, Integrity asks you to refresh it instead of applying a different move than the one you reviewed.
Issue-only and subtree moves
When a selected Issue has descendants, the dialog can move only the selected Issues or include their subtrees. Subtree moves carry active and archived descendants to the destination Team, deduplicate overlapping selections, and preserve internal parent/sub-issue links inside the moved set.
Issue-only moves detach the moved Issue from outside parent/sub-issue links so the source Team does not keep a hidden cross-Team hierarchy.
Because Cycles are owned by a Team, moved Issues leave their current Cycle. Integrity does not automatically add them to a destination Cycle.
History and old links
Moves keep the Issue history continuous. Team identifier aliases cover renamed prefixes, while Issue-key aliases cover deliberate cross-Team moves. An old key redirects to the current key only when the viewer may still access the moved Issue; hidden callers receive no Issue detail.
Move activity appears in the Issue Activity timeline for every moved Issue. Subscriber-visible move notifications are Inbox-first and active-Issue-only; archived descendants retain their Activity history without a normal actionable Inbox notification. Team moves do not send Issue activity email.
Private Team behavior
The move command appears only when every selected Issue is active and editable. Destination Teams appear only when you can work on their Issues. Integrity rechecks the selected Issues, every source Team, and the destination Team while the dialog is open and again on the server before committing.
Private Team names, identifiers, routes, label names, status names, and old Team context are hidden or redacted when the viewer lacks access.
Review the preview carefully before confirming. Moving an Issue can change the visible key, status, labels, and eligible assignee.