You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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?
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.