Clone epic issue with set of linked standard issues

Question

Hi

I would like to clone an epic with a set of linked tasks by entering a new name for the epic before copying it. These cannot be sub-tasks as I will not be able to see them on the timeline.

Linked tasks has a specific issue.type and the name of epic shoudl be copied do their summary.

Can you advise me how to do this? Please?

What I managed to get myself was to copy only the epic.

Akhand Pratap Singh_z78moi · Accepted Answer

Hello @Emilia KASPRZYK ,

As the ask is to manually enter the summary of the Epic every time you clone it, I am not able to suggest a direct easy solution.

But a couple of Automations would do that.

Note: I am considering when you clone the epic, you do not want to clone the linked issues as well, you just want to create a new set of linked issues to the new cloned Epic.

Automation 1:

Trigger: Create an Automation with a Manual trigger from issue, so which ever Epic you want to clone, you can use that Automation from that issue itself,

Condition: issuetype = Epic

Branch: For most recently created issue

Action:

* Create a variable to store the new Epic key
* Create an issue: and link to the variable which you created to store key (you can clone the action to create multiple linked issues)

Automation 2:

You can use this Automation to update the Epic name of the cloned ticket and once that is done, update the linked issues Summary to store Epic name in it.

Let me know if this works or if you have any questions

Luka Hummel - codefortynine · Accepted Answer

Hi there!

If you're looking to clone an epic along with its linked standard issues — where the issues aren't sub-tasks but need to retain specific link types and a customized summary — our app Deep Clone for Jira is the perfect solution.

With our Epic/Tree Clone feature, you can:

* Clone an epic and its entire hierarchy of linked issues (e.g., tasks, stories, bugs) while maintaining the structure and issue links.
* Use the Field Editor with Jira Expressions to automatically update summaries or other fields of the cloned issues, such as appending the new epic name to each linked issue’s summary.
* Clone additional issue data such as comments, attachments, work logs, and even issue status (given compatible workflows).

This makes Deep Clone for Jira an excellent choice for duplicating standardized epic structures for recurring work or templates, all while keeping full control over the cloned content.