Automation: clone to dynamic project

Esther Strom

I've done a ton of cloning to other projects via automation, but it's always specified in the rule which project to clone into.

I now have a project that has a Project Picker field type on the bug screen, to allow a user to choose a destination project. I want to use the value of that field in my automation rule to determine which project to clone into, but the Project field in the clone step doesn't want to accept smart values.

I can type the smart value for the field into the Project field in the rule, but as soon as I move out of that field, it immediately changes back to Same Project.

Is this possible? Or is there another way to do this? (I've tried both Clone and Create Issue actions; same result.)

Mark Segall

Hi @Esther Strom - You need to use the project ID (e.g. 12345) to set the Project in the Clone/Create Issue actions.  There are two ways you can handle this:

1. If you're using JSM premium you have Assets.  You could create an object type for projects with an attribute for Project ID.  Then your project picker can use a custom asset field.  This method is extra helpful because you can automate populating new projects and you can have different attributes that use as flags for when/when not to make projects available to the picker.  
2. Use cascade select custom field with the parent value being the project name and the child value as the project id.  Then you can extract the project ID for your clone action