How to clone a specified JIRA story

[kunal.matharu]

The goal is to have a placeholder where I could click an automation "XY" and I would want to specify one or two stories to clone in a series so there subtask could be also cloned. Currently JIRA has no support for nested for loops hence why I'm looking to specify the story I tried the following approach, but I need help to assign the lookup value to the clone issue function.

[Trudy Claspill · Accepted solution]

Hello @kunal.matharu 

It is unclear to me what you expect this rule to do?

Are you trying to clone the issues found by the Lookup Issues action? And then clone the subtasks of those issues into the newly created issues?

[kunal.matharu]

Hi Trudy yes that is the steps I would like to take 

  - Use a random place holder to call the Automation (Manual Trigger)
  - Lookup the Issue (a single story)
  - Clone the issues found by the Lookup Issues action
  - Then clone the subtasks of those issues into the newly created issues

[Trudy Claspill]

Is the rule going to look up the same single issue to clone every time?

Is that going to be a "live" issue that gets updated such that the set of subtasks or data in the issue might change periodically? Or is it a "template" issue that is changed infrequently?

[kunal.matharu]

The automation will have this same format for three stories to lookup and clone with their subtasks. I would run it every three months.  

[Trudy Claspill]

Do you want to create one rule to clone all three issues, or three separate rules to clone one issue each?

Are the issues you want to clone likely to change frequently, or will they remain static? How many subtasks will there be for each issue?

If they are likely to remain static, or change rarely, and there are not too many subtasks, then a simpler solution may be to construct a rule that creates the issues directly rather than cloning existing issues.

[kunal.matharu]

Do you want to create one rule to clone all three issues, or three separate rules to clone one issue each?  One Rule 

Are the issues you want to clone likely to change frequently, or will they remain static? How many subtasks will there be for each issue? Static

If they are likely to remain static, or change rarely, and there are not too many subtasks, then a simpler solution may be to construct a rule that creates the issues directly rather than cloning existing issues. Let me give it a try. 

[Trudy Claspill]

If you want to create the issues and subtasks from static data rather than cloning, the rule would look like this:

In the Create Variable step you create a variable to hold the issue key of the parent issue you just created.

In the Create Issue / Subtask steps you use that variable to set the parent of the subtask.

[Trudy Claspill]

Hello @kunal.matharu 

Were you able to address your requirement with the responses I provided?

If so, please consider clicking on the Accept Answer button above my response thread to mark your Question as Solved.

[Luka Hummel - codefortynine]

Hi @kunal.matharu,

If you are willing to use a third party app, our app Deep Clone for Jira can be a great solution for your use case. It allows you to:

• Clone single or multiple issues at once.
• Include subtasks, issue links, attachments, and comments.
• Use Epic/Tree Clone to duplicate an issue along with its entire hierarchy.
• Integrate with Jira Automation to automate cloning processes.

[kunal.matharu]

Unfortunately not the solution I am looking for.