*** How moving works The ticket is removed from the original workspace and added to the destination workspace with all its history intact. The ticket mirror in the original workspace’s triage channel is updated with a “moved” indicator showing where the ticket was relocated. A new mirror is automatically created in the destination workspace’s triage channel. All stakeholders (assignee, followers, requester) are notified of the workspace change with context about the new location. Request thread mirrors, DM mirrors, and triage channel mirrors are all updated to reflect the workspace change. The following information is preserved: * **Ticket history**: All messages, comments, and activity * **Properties**: Status, priority, tags, categories, custom fields * **Relationships**: Linked tickets, parent/child relationships * **Attachments**: Files and images attached to the ticket * **Time tracking**: SLA timers and due dates The following elements change: * **Ticket ID**: The ticket receives a new ID based on the destination workspace’s channel prefix * **Assignee**: May need to be reassigned if the original assignee is not a member of the destination workspace * **Channel**: The ticket is assigned to the default channel in the destination workspace * **Followers**: Followers who are not members of the destination workspace are removed *** Move a ticket Navigate to the ticket you want to move in Ravenna. Click the **More actions** menu (three dots) in the ticket header. Select **Move to workspace** from the dropdown menu. Select the destination workspace from the list of available workspaces. Review the change and click **Move** to complete the transfer. Moving tickets cannot be undone. Make sure you’re moving to the correct workspace before confirming. *** Use cases Move complex issues to specialized teams or leadership workspaces for higher-level attention. Fix tickets that were created in the wrong workspace due to initial misrouting. Transfer requests that span multiple departments, such as moving from IT to HR or between cross-functional teams.

Documentation Index