In JSM, how do we move tasks from one project to another?

Pat Rodgers_siqrom

We're building out three different teams. Team A uses our Help Desk Project, Team B uses the Application Team Project. The end users sometimes don't place tickets into the correct Team's project. I noticed today that there isn't an option to move a task between the two projects and assume I will have to build an automation for this?

Jaime Escribano _knowmad mood_

Hi Patrick! Glad to see you reached out to the community!

Your options would be:

Manual Move : Jira admins can move issues between projects by editing the issue and using the "Move" function. During the move, you'll need to reassign the request type and map any fields that don't align. This is not super recommended as it's both tedious and error prone.

Automation Workaround: You can set up an automation rule that clones the issue to the correct project based on certain conditions (like keywords or request type), then optionally closes or flags the original issue. It won’t be a true “move,” but it can replicate the behavior. You can make it a manually triggered automation or tie it to a workflow (that last option can help gather data on how often people mis-create issues)
Just make sure you let the user know their ticket was closed and a new one was created in it's place! You can do so using smartvalues. The client will need to be added as a participant to the newly created ticket Also, they will need permissions in both projects.

Hope that helped! Let me know if you have any doubts!