clone epic with child issues

[marion.hillion]

Hi everyone,

I am trying to clone an Epic along with all its linked tickets from the same project in Jira. I've attached a screenshot to this message, which provides an example of what I would like to duplicate. In the screenshot, you can see the Epic and its associated tickets.

I have attempted to use an automation rule that I found on your forum (attached as a screenshot), but unfortunately, it doesn't seem to be working as expected (sorry my screen is in french)

I would greatly appreciate it if you could guide me on the correct steps to achieve this task or provide any insights you may have. If there's a different approach or if there are additional settings that need adjustment, please let me know.

Thank you so much for your time and assistance. I look forward to hearing from you soon.

Best regards,

[Luka Hummel - codefortynine]

Hi @marion.hillion

If you are willing to use a third-party app, you can try our app Deep Clone for Jira.

Deep Clone can easily clone whole issue hierarchies, in your case an Epic with all its linked issues, with our Epic/Tree Clone feature. Additionally, Deep Clone has multiple features that can help you with your workflow. 

1. Clone Links and Sub-Tasks: It ensures that not only the main issue (Epic in your case) but also all linked issues, sub-tasks, and even attachments are cloned.
2. Preserve Hierarchies: The app respects and maintains the hierarchy of issues, which is crucial when working with Epics and their child issues.
3. Customizable: You can configure what elements you want to clone (like comments, links, etc.) and even automate the cloning process.

[Clara Belin-Brosseau_Elements]

Hello @marion.hillion

If automation doesn’t work for you and 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 clone your Epics with all its linked tickets.

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.

Clara

[Bill Sheboy]

Hi @marion.hillion 

What is not working as expected when you use the rule?

You appear to be using a team-managed project.  Would you please confirm that?

Would you please show an image of the audit log details from the execution of your rule, and some additional images of the rule:

• the details of the create variable action
• the details of the create issue action, which should be using that created variable

This additional information may provide context to explain what you are observing.  Thank you!

Kind regards,
Bill

[Charles Liss]

I am curious why a team-managed project matters in this case.  

[Bill Sheboy]

Hi @Charles Liss 

For automation-related questions, I find knowing the full context for a rule helps to know what is / is not relevant to the symptoms being observed.

Team-managed projects (TMP) each have their own configurations for issue types, etc.  With automation rules, people may assume the behaviors they were accustomed to for many years with company-managed (CMP), which shared configurations.  And only in the last year, or so, did the parent / child linking method align between the different project types.  This became less relevant because...

The only follow-up from the original poster seemed to indicate they thought the automation Clone action cloned an entire tree of issues, which is not the case.

Kind regards,
Bill

[Arensa Prasta]

Hi @marion.hillion I am not clear why would you need an automation for this case. But in case this is not a recurrent action and you just need to clone your epic, open the epic and find the Clone option under the three dots. 

[marion.hillion]

Thank your for your help. The problem is that the cloning process seems to only replicate the Epic itself without its associated tasks. As a result, the cloned Epic appears empty, lacking the linked tickets that are crucial to our workflow.