Create an automation to clone a ticket, but ask issue type of target ticket

[Dale Bronk]

I'm setting up an automation called "Send to Development".  When I trigger I want it to clone the ticket into a development project and set a link between the two tickets in each project.  Easy-Peasy.  I have that setup.  The issue I have is that in the clone action it makes me set the issue type for the target.  Most of the time it will be bug, but not always so I set up the automation to prompt me with the Development Ticket Type and have a drop down for Story, Task, Bug.  I want whatever I select to be the ticket type of the new ticket created from the clone.  Otherwise I'll just default it to Bug and when it is not I'll just go into the other project and manually change that ticket type.

[Trudy Claspill · Accepted solution]

Hello @Dale Bronk 

Welcome to the Atlassian community.

You can do this with a Lookup Table.

https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Create-lookup-table

Let us say you are prompting for the destination issue type like this.

Create a Lookup Table that maps the value options in your prompt to the actual numeric ID associated with that issue type.

You can then use the smart value for retrieving the Lookup Table value matching the value selected during the prompting to set the issue type in the Clone action.

Make sure that you type in all the names/smart values in a case-sensitive manner.

[Dale Bronk]

Thank you.  I've requested to our admin to install the lookup manager plugin.  I'm now waiting for that and then will give this a go.  Looks very straight forward and exactly what I'm looking for.

[Trudy Claspill]

My suggestion does not require any additional apps be added to your instance.

All of the functionality I described is native to the Automation Rules feature in Jira Cloud.

[Dale Bronk]

hmmmm.  Then can you give me some details on how to get to the lookup table page?  I google it and it says I need to install the Lookup Manager plugin.

[Trudy Claspill]

There are UI changes being rolled out to the Automation Rules feature, and I appear to now be on the new UI. Your UI may not look the same (yet), but the text description of the steps is the same.

Add a step to the rule.

Elect to add an Action type of step.

Search for the action name "lookup"

Select the Create Lookup Table action.

[Dale Bronk]

Thank you!  Yep, my UI was a bit different but got it done and tested.  Not sure what the Lookup Manager plugin gives me but certainly did not need it.

[Trudy Claspill]

Great!

If my answer has helped you solve your requirement please consider clicking on the Accept Answer button.

[Luka Hummel - codefortynine]

Hi @Dale Bronk

I'm Luka from codefortynine 👋

If you are willing to use a third-party app, our app Deep Clone for Jira offers a suitable solution. Deep Clone allows for advanced features not available in the standard Jira clone function. Specifically, it enables you to edit the issue type for both single and bulk clones​​.

You can create a preset where you configure your clone and add the preset to the issues Actions menu ··· with the Create and confirm option selected to be able to select the target issue type.

[Dale Bronk]

Thanks.  I'll take a look at your plugin when I get some time.  For now, Trudy's answer got me what I needed.