# Ticket auto assignment when the pipeline is changed **URL:** \ **Category:** Tickets & Conversations\ **Tags:** help-desk\ **Created:** [June 19, 2024, 3:52pm UTC](https://community.hubspot.com/t/ticket-auto-assignment-when-the-pipeline-is-changed/109686 "2024-06-19T15:52:50Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![DanaIrvine](https://avatars.discourse-cdn.com/v4/letter/d/f4b2a3/32.png) [@DanaIrvine](https://community.hubspot.com/u/DanaIrvine)\ **Post date:** [June 19, 2024, 3:52pm UTC](https://community.hubspot.com/t/ticket-auto-assignment-when-the-pipeline-is-changed/109686/1 "2024-06-19T15:52:50Z")
Here’s my scenario: A ticket is created and auto assigned to a user. The user determines that the ticket was created in the wrong pipeline and moves the ticket to the correct pipeline. When this happens, there is no auto assignment that takes place. How can I trigger the auto assignment of the ticket when this happens? ---
**Author:** ![Shubham\_Sharma](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/shubham_sharma/32/20922_2.png) [@Shubham\_Sharma](https://community.hubspot.com/u/Shubham_Sharma)\ **Post date:** [June 20, 2024, 7:12am UTC](https://community.hubspot.com/t/ticket-auto-assignment-when-the-pipeline-is-changed/109686/2 "2024-06-20T07:12:24Z")
Hey @DanaIrvine To trigger the auto-assignment of a ticket when it is moved to a different pipeline, you can use the workflow feature in HubSpot: In your HubSpot account, navigate to Automation and then to Workflows Create a new workflow and select Ticket-based. Set your enrollment trigger based on the ticket’s movement to a different pipeline or status. Add an action for rotate ticket to owner, which will automatically assign the ticket to a new owner based on your specified criteria.Make sure to checkmark overwrite if the ticket has an existing owner, to ensure the new assignment takes precedence over any previous assignments. To undersand this better you can go through this HubSpot acdemy lesson: [HubSpot Academy](https://app.hubspot.com/academy/45745386/lessons/808/4108?language=EN) Let me know if you have any followup questions! ---
**Author:** ![DanaIrvine](https://avatars.discourse-cdn.com/v4/letter/d/f4b2a3/32.png) [@DanaIrvine](https://community.hubspot.com/u/DanaIrvine)\ **Post date:** [June 20, 2024, 3:20pm UTC](https://community.hubspot.com/t/ticket-auto-assignment-when-the-pipeline-is-changed/109686/3 "2024-06-20T15:20:01Z")
Thank you!! ---
**Author:** ![DanaIrvine](https://avatars.discourse-cdn.com/v4/letter/d/f4b2a3/32.png) [@DanaIrvine](https://community.hubspot.com/u/DanaIrvine)\ **Post date:** [June 20, 2024, 4:50pm UTC](https://community.hubspot.com/t/ticket-auto-assignment-when-the-pipeline-is-changed/109686/4 "2024-06-20T16:50:56Z")
Yhis almost works. The regular assignment rule only asigns to users who are available, this assigned to anyone in the team, even users who are marked away. 😞 ---
**Author:** ![Shubham\_Sharma](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/shubham_sharma/32/20922_2.png) [@Shubham\_Sharma](https://community.hubspot.com/u/Shubham_Sharma)\ **Post date:** [June 21, 2024, 5:05am UTC](https://community.hubspot.com/t/ticket-auto-assignment-when-the-pipeline-is-changed/109686/5 "2024-06-21T05:05:46Z")
You’re welcome @DanaIrvine If my answer resolved your query, kindly mark it as the accepted solution. Thank you! ---
**Author:** ![CGrove5](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/cgrove5/32/80838_2.png) [@CGrove5](https://community.hubspot.com/u/CGrove5)\ **Post date:** [October 2, 2026, 1:10pm UTC](https://community.hubspot.com/t/ticket-auto-assignment-when-the-pipeline-is-changed/109686/6 "2026-10-02T13:10:01Z")
@DanaIrvine This is a quick one to set up with a ticket workflow. Here’s how I’d do it: - Go to Automation, then Workflows, and create a ticket-based workflow - Set the enrollment trigger to Ticket pipeline is any of the pipeline you move tickets into - Add the “Rotate record to owner” action and pick your team or users - Turn on the option to overwrite the current owner - Turn on re-enrollment so tickets that move again get reassigned Without the overwrite setting, tickets that already have an owner just keep it, and that’s the usual reason it seems broken. Test with one ticket before turning it on for everyone.