You're dealing with Workspace limitations when forwarding tickets between different environments. Typically, forwarding to an external Workspace email should work unless restrictions are in place. If forwarding isn't an option, using the Move functionality might be necessary. However, you could explore these alternatives:

1. Allowlist the Email: Check if the receiving Workspace blocks external emails and allowlist the IT Workspace's email.
2. Shared Mailbox Access: If both teams need to collaborate, setting up a shared mailbox across Workspaces might help.
3. Automated Rules: Some Workspace platforms allow auto-forwarding rules for seamless communication.

Would love to know what platform you're using—there might be specific settings to tweak!

Is this a bot response?
The first alternative doesn’t make any sense in context.

yes bot. FW drops e-mail sent from one FS mailbox to another FS mailbox. cloning the ticket or create a subticket. 

Thanks.
I’m assuming there’s no way around the hardcoded ticket loop prevention when sending from one Workspace email to another, even with skip email notification present?

No, I have a idea of using a sidebar app, where you select the workspace and group. It clones the ticket. 
Still The idea is to get feedback from the other group on a ticket.  Create tasks or child ticket that you assign the to the other group. 

This was Freshdesk ? ignore the task bit then :) 

I like this idea!
We have the clone ticket app but it’s still extra steps for those involved which they can’t seem to learn, everyone in our Business Workspaces has been forwarding emails for years now and untraining this behaviour is difficult.
I’ve managed to figure something out in my other thread 

but it’s very janky, so an app that could just do this easily would be a great solution.

EDIT: Is Freshservice not Freshdesk

​@Kamakshi V can you please move this thread to FS ? 

Hi,

In our freshservice, we setup a workflow to copy the ticket description and than put this as a body and use the workspace_id to send it to the associated workspace
 

You can setup someting to delete or close the main ticket too if needed

Managing workflows between separate workspaces can sometimes create unexpected challenges, especially when trying to forward emails between teams. It sounds like a streamlined solution for forwarding might be the best approach rather than moving tickets entirely, but this depends on your system’s configuration. If you’re dealing with time-sensitive tasks, similar complexities can arise in other areas too, like when trying to track Sunni prayer time variations in Riyadh—it’s important to rely on accurate systems for consistent results. For further help on integrating systems or troubleshooting these kinds of setups, I highly recommend checking out the Freshworks Community, where you might find more insights on this.

ya using API to create a new ticket is better and I think if you build a app you can even have that in the sidebar.