Currently moving issues from one project to another is rather cumbersome and time consuming. On an average of almost 5 minutes and 10 screens to move one item or multiple items into another project. We frequently move items from one project into another after product planning is complete and the issues are ready to be worked in the development project.
I don't see an 'action' to move in JIRA automation (i see the move trigger) and was wondering if this was even possible. Ideally I'd like the ability to forgo all of the validation screens that trigger during a move, since they are always the same, to improve and speed up this process.
Unfortunately those validation screens are there to ensure that the issue can be moved correctly and map values if needed because moving an issue in Jira is actually one of the most complicated things to do under the hood (Except bulk move). It is the reason they don't expose this functionality via REST - it simply too complicated.
As such, we have no way of doing it either in cloud and even in server it would be hard to capture enough information to make this possible.
Sorry that we can't support this use case right now.
We do see a lot of other customers simply cloning the issue or creating a new one in the another project and then linking them.
This is usually "good enough" for a lot of use-cases.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
This September 6-7, hundreds of Atlassian App developers will flock to Barcelona Spain to build skills, discover product roadmaps, meet face-to-face with the Atlassian team, and learn how to extend t...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs