How to properly duplicate an issue in a another project

[Michael Berkowitz]

I have a customer support project with a bunch of issue custom fields. If the issue needs to get escalated to a defect in another project, I would like the original issue to stay and the new issue in the other project to inherit all the matching field values from the original issue.

Cloning does not seem to work across projects and moving will erase the orginal issue. Linking will not automatically populate the field values in the new issue.

All suggestions greatly appreciated.

[Lee Correll]

Bob, I've been looking for that "move" mechanism via CLI / REST, but been unable to do so. We do the clone/move thing regularly, but since shifting to OnDemand, have noted that we lost a bunch of functionality in doing so, and are now having to perform a number of tasks manually that we didn't before. Is there a way to do this that I'm not seeing?

Thanks!

[Renjith Pillai]

Clone and move?

[Bob Swift (personal)]

JIRA Clone-Plus plugin . Oops, its on demand, you can't install plugins with OnDemand :(.