Relationship to ticket in higher hierarchy gets lost in a clone

[Martina Guth]

Hi,

We want to clone an Epic that is a child of or relates to a Demand. But when cloning the Epic, the relation to the Demand gets lost in the cloned ticket. Is that a bug or is there any reason for that?

Thankful for advice,

Martina

[John Funk]

Hi Martina - Welcome to the Atlassian Community!

How are you doing the clone? 

[Martina Guth]

Hi John,

click the three points on the right top and clone - so I would say, Atlassian native.

[John Funk]

That seems like a bug then. You might try a manual automation rule and see if that helps. 

[Martina Guth]

Thank you, will try and respond. :-)

[Martina Guth]

A very good colleague from our external partner found out, what I did wrong. Maybe also interesting for someone of you. 

You need to tick "links", when cloning, then it works :-)

[Luka Hummel - codefortynine]

Hi @Martina Guth,

When cloning an Epic in Jira, certain relationships or links to parent or related tickets can indeed get lost, depending on the cloning method being used. This behavior is typically not considered a bug but rather a limitation of the default cloning functionality in Jira.

To address this issue, you could try our app Deep Clone for Jira. Deep Clone offers advanced cloning features, including the ability to clone issues along with their hierarchy and relationships with its Epic/Tree Clone feature. This app ensures that links, sub-tasks, and other related elements are preserved in the cloned ticket.

Here's how Deep Clone can help in your case:

• Clone Epics with all related tasks: Maintain the structure and relationships of your Epics and their associated tasks.
• Preserve links: Ensure that links to parent issues, such as Demands, are retained in the cloned issues.
• Bulk cloning: Clone multiple issues at once, saving time and effort.