How to move issue from one project to other using custom groovy script?

[Prashant Mali]

I want to move issue to specific project using post function.

Awaiting your response.

[Nic Brough -Adaptavist-]

No.

You cannot do this in a post function, as you need the issue to not be in the middle of a transition.

Moving an issue is complex whenever you do it.  The project (and issue type) define ALL the configuration for an issue, and to avoid breaking your data, Jira checks compatibility when you do a move.  What happens when the workflow is different in the new project?  Or security, or fields or or or?

The question "move issue in post function" is not in itself a bad question, but it always points to a wider problem.  Either your process is broken, or you are mapping it into Jira incorrectly.

Instead of trying to perform a hideous botch with complex code, fix your process or mapping.  Go back to the source of the question - why do you think you want to move an issue in a post-function?

[Prashant Mali]

It is not moving the existing issue to a new project. The requirement is Make a clone of existing issue and move that cloned issue.

[Nic Brough -Adaptavist-]

Ok, that's not in the original question, so there was no way to know.  

It is easier in some ways, as you can move an issue if it's not the issue being transitioned, but your code will still need to think about ensuring your "clone" is complete before trying the move.

The comments about moving issues still stands though - it's hard, complex and potentially messy.

Frankly, just don't bother.  Instead, write a simple "create issue in other project, with any fields from the current issue copied in".  You don't need to mess around with clone or move.