Manual Automation to clone into other projects

Matt Heidsick April 5, 2024

I am working on some automation for my team to clone Epics from our project into other teams spaces. Is there a way to prompt for the project the epic needs to be cloned into??

i.e. My Epic is in A and I need to clone it to project B. I'd like to click Actions > Clone and then receive a prompt with drop down B, C, D where I can then select B and the automation will then run and clone it into Project B. Right now I have it running into a predetermined project but I want there to be a prompt with the selection.

Thank you in advance. 

Matt

3 answers

1 accepted

2 votes
Answer accepted
Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 5, 2024

Another option is to still use the Manual Trigger input, and get the user to provide a known value (or provide them with a selection list)

Use the Create Lookup Table action and create a table that links those possible inputs to the numeric ID of the related project.

Screenshot 2024-04-05 at 1.38.05 PM.png

Then you don't need to use an IF-ELSE structure to evaluate the input. Instead you use a smart value in the Create/Clone issue step.

Screenshot 2024-04-05 at 1.40.09 PM.png

Matt Heidsick April 7, 2024

So I tried that with but got an error message. After a bit of back and forth I figured out that instead of {{projectKeys.get(userInputs.destProjects)}} I had to use {{projectKeys.get(userInputs.projectKeys)}} instead.

Here's my config:

 Screenshot 2024-04-07 103757.png

That did the trick. Thank you !!!

Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 7, 2024

You would need to use the Variable Name that you assigned to the input you defined in the manual trigger. In my case that was "destProject". In the response from @Kalyan Sattaluri that was "MYFIELD".

{{table-name.get(userInputs.variable-name)}}

Like Matt Heidsick likes this
Matt Heidsick April 7, 2024

Yes, that's what I figured :) I am pretty new to this and had never worked with Variables before and assumed that the destProject was a system variable to assign the project key. I don't know ...... it works now, that's all that matters. :D 
Thank you again for the help !!

1 vote
Kalyan Sattaluri
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
April 5, 2024

Hello @Matt Heidsick 

Please look into user input section of manual trigger, how to create drop down etc. 

Then you  can do If condition, smartvalue check, and check user value to create accordingly..

image.png

hope it helps.

0 votes
Clara Belin-Brosseau_Elements
Atlassian Partner
April 11, 2024

Hello @Matt Heidsick

 

If you're willing to use a third-party application, I can suggest trying our Elements Copy & Sync app that allows you to copy issues with all their content (summary, description, custom fields, comments, attachments, etc.) and their child issues.

 

You’ll be able to easily manually clone your Epics from project A to project B.

 

Don't hesitate to try our app, it's free during 30 days and stays free under 10 users.

Let me know if you have any questions.

 

Kind regards,

Clara

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events