how to park ticket to another department
ART-15989_KNOWLEDGE_NODE-25
successful validation, the snap-in relocates the issue or ticket to the part specified in the **Issue/Ticket - Target Part Field**.\n\nInstallation\n------------\n\n1. Open the DevRev marketplace and install the **Automated Part Update** snap-in.\n2. Select the workspace where you want to install the snap-in, confirm your\n   selection, and click **Deploy snap-in**.\n3. Set the following operating parameters.\n\n* **For Initial Part of Issue**: Enter the part to be used as a condition for the
Automated part update | Automate | Snap-ins | DevRev
ART-1976_KNOWLEDGE_NODE-25
and effective resolution. Users can design workflows tailored to various scenarios; the example below illustrates a basic routing use case.\n\n| NODE | ACTIVITY |\n| --- | --- |\n| Trigger | Ticket created |\n| Action | Pick user by group |\n| Action | Update ticket |\n|  | ID: Ticket created > Output > ID |\n|  | Group > Output > ID |\n|  | Owned by > Set: Pick user > Output > User |\n\nOrgs can set up pull-based routing by updating the group instead of the user ID in the workflow illustrated
Routing | Computer for Support Teams | DevRev