Ok, so the standard advice about moving issues between projects is "don't". Moving an issue is a clunky manual process, and can't be done in a workflow or automatically.
It is generally a thing you do rarely, when someone genuinely makes a mistake and creates something in the wrong project, or when you're doing some housekeeping and want to rearrange your project usage.
It should not be done as a standard process, it's an exception.
I can completely understand the desire to move an issue from a Service Desk project out into a development or tracking project, but you shouldn't.
It is exactly as you suspect, you will lose the ability to communicate with the customer if you move an issue from a Service Desk project into a development or tracking project - you'll lose the customer request that is sitting in front of the issue, which is the thing doing all the communications. It won't exist in the development/tracking project.
So, yes, you would be better off cloning into the development project. I would suggest the agent uses the "create issue in development project" option though, that will retain the link between Request -> Service Desk Issue -> Development issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.