Are you moving between projects or between workflows within a project? Moving issues can be complex and require human intervention to direct the move, e.g. current status doesn’t intuitively map to new project status. Moreover, automation of moving issues leads me to think this is a broken process. Moves absolutely make sense to ‘clean up things’ initially done incorrectly.
With all that said, AFAIK, Automation does not support Move. Assuming I am correct and you do not see this action in Automation then you would need some other addon to make this happen.
That isn't possible in Jira.
Using Automation, you could clone the issue and delete the current issue - but to actually move them is a manual process.
Hope that helps,
Regards, Liam
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
How would I add the delete function? After cloning, Branch Rule, then delete current issue?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Automation doesn't do this.
HOWEVER, you can create a trigger that creates a new issue in another project. You can copy values from the parent ticket into the new ticket - which could do the same thing, but you'd end up with 2 tickets in the end.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.