Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

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

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

Awaiting your response.

1 answer

2 votes


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?

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.

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.

Like Adam Hraban likes this

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events