Copy-to-Development workflow

Problem Definition

We've setup a dedicated service desk project, so we can have the issue types, workflows and so forth setup to suit/match the service desk workflow.

If an issue gets pushed across to the developer team, we then have a choice: Do we move the issue (and lose the tracking, SLAs etc in the service desk) or clone it and then move it (which "wastes" an ID and leaves gaps in the issue numbering).

Suggested Solution

It would be nice to have a simple "Send to Developers" or "Copy to Project" workflow which creates a duplicate of the issue in the (specified) developer project, and automatically links the service desk project issue to the developer project issue.

That would mean you can have a single helpdesk project for triaging issues, and the development team the flexibility to play around with the issue without impacting the SD team and metrics.