I need to clone and move an issue to another project in one step without define the project

Anita Hütter_zsxo7p

Until now we made a clone issue postfunction and after the clients had to move the issue to another project in a second step - they can choose the project from the drop down.

 

Do you see a possibility to combine the two steps? If you perform the transition they get the drop down to choose the project where the clone should be created.

Mark Segall

Hi @Anita Hütter and welcome to the community!

This will require a different way of thinking and it won't be possible with workflows alone.  You'll want to consider using Jira automation.

First, you cannot MOVE issues in an automated way.  Instead, you should approach it where the clone is created directly on the target project.  This is where automation comes in and even then, you're going to need the project ID to be able to accomplish this. So, you probably want to update your project picker to be something like "Project Name|Project ID" (e.g. Test|10001).  It's not pretty from a UI perspective, but it's the easiest way to ensure the project ID is captured.

Once you have that, your automation rule would look something like this:

• TRIGGER: Issue Transitioned (Whatever status is triggering the clone)
• ACTION: Clone Issue
  • Project

    • {{issue.YourProjectPicker.value.subStringAfter("|")}}

  • Any other fields you want to update

This will trigger when the issue transitions to the desired status and then set the target project accordingly.