How can I use automation to clone a ticket in another project

[Scott Federman]

Hey all, 

Here are the details. I have a primary project (NMPM) that is supposed to kick off activity in another project (CCEC). When my issue in NMPM is transitioned to the "SIA" status, I need it to clone CCEC-457 as a new ticket in the CCEC project and link it back to the NMPM project. Is this process possible using automation? If so how? So far this is what i have but i don't know how to specify that i want it to clone CCEC-457.

[Scott Federman · Accepted solution]

Ok so the solution was actually very simple.  Do it from the global automation level. Use a branch and clone from there. 

[Clara Belin-Brosseau_Elements]

Hello @Scott Federman, 

As an alternative to Automation (that can be complex sometimes), I would suggest trying our app Elements Copy & Sync to automatically clone your issue into the CCEC project on a status change.

The app allows you to clone and sync a full hierarchy of issues with all their content (summary, description, custom fields, comments, attachments, etc). You can trigger the cloning based on status change to automate it.

Don't hesitate to check the documentation and try the app for yourself (its free during 30 days), it’s really quick and easy to set up.

[Scott Federman]

unfortunately for us the security review and procurement process takes far longer than i have time for to obtain a new addon

[Cristian0791]

Hi Scott,

Try to change Then: Create a New with Then: Clone issue into 

Also you will need to specify the issue type and what field you want to clone in the new issue.

Hope this helps.

[Scott Federman]

hey @Cristian0791 yes sorry i switched to create to test something but it didnt matter. I  switched back to clone but the problem is you can define specifically what ticket you want to clone. only the project you want to clone.