So this is a hard one if you are looking to maintain the original ticket in that specific pipeline, and not just move it into the next step. In theory you can just move that ticket to the next pipeline and keep going, but it would no longer appear in the previous queue as something worked.
Do you have access to workflow tools? In those cases, once one of the earlier pipeline tickets is completed you could write a workflow to create a new ticket with almost all the data mapped over to the fields. I say almost because the one-piece that cant be transferred this way would be items such as calls/notes/etc.
Honestly, I like in these cases to simply advance a ticket into the new pipeline. It keeps all the data moving, you can look at it stats wise as saying if it is in this stage, it must have progress previously through the over pipeline successfully. It just saves so much time and effort to just trip it over into the new pipeline queue when it is completed in the first.
If you are not using notes sections, and just field data. The other approach I mentioned of using a workflow to simply create the new ticket in the process is also possible.
Hope that helps a bit, I haven't had my morning coffee yet... so not sure if I am making sense or not.
I want to tag in a few subject matter experts who may be able to assist with this! @darynsmith, @joshua-paul, @JustinPerkinsC do you have any suggestions?
Thanks!
Jess
Wusstest du, dass es auch eine DACH-Community gibt? Nimm an regionalen Unterhaltungen teil, in dem du deine Spracheinstellungen änderst !
Did you know that the Community is available in other languages? Join regional conversations by changing your language settings !