Remove Clone Link from Original and Cloned Option

[orla_mears]

Hi all,

Been trying multiple automation rules but not yielding any success. I have a "Master" Work item in a project (company managed) and when I clone from this work item, both work items show that they are cloned to or from their originating work items.

I've tried multiple rule various but none are working.  Has anyone successfully been able to set up a rule that would command:

Work item is created (specifically, cloned)
Original Work item does not show any direct link to new cloned work item
Newly cloned work item does not show any direct link to original work item it's cloned from

Thanks!

[Luka Hummel - codefortynine]

Hi @orla_mears

Jira automatically adds a "clones" issue link between the original and cloned issues when using the standard Clone function. If you'd like to prevent this link from being created when cloning issues, our app Deep Clone for Jira offers a flexible solution.

With Deep Clone, you can simply uncheck the option Add issue links between clone and original issue.

As an additional benefit, Deep Clone also supports advanced cloning features like cloning issue status, comments, subtasks, and custom fields, which go beyond Jira’s built-in capabilities.

If you frequently work with templates or need to clone across projects or instances, you might also be interested in Deep Clone’s Presets or the Post Function Clone to automate these operations.

[Marc - Devoteam]

Hi @orla_mears 

This is not possible.

On cloning by design the a link is set between the original work item and the cloned item.

Are you cloning via automation or the cloning option on the issue?

If you would use an automation rule to clone a work item, you could try to set a branch in the rule and base the branch on the most recently created work item and then delete the link and a branch on current item and delete the link

[orla_mears]

Hey @Marc - Devoteam thanks for reaching out - I have set a master work item that team members can essentially clone (including tasks and sub-tasks) to reduce manual effort on repeat tasks.

It looks like the rule you have above would clone a work item into the same project every time? If so that wouldn't work, I essentially just wanted to remove any inherent association between the master work item and the one they will clone, as there's no requirement for them to be linked.

[Marc - Devoteam]

Hi @orla_mears 

This is an example, adjust this to your needs.

[Yogesh Mude]

@orla_mears  Could you please share your rule snap, its better to understand what you are able to acheive with the automation and can suggest.

[orla_mears]

@Yogesh Mude  Got this reference from AI - evidently not correct hence why I was looking for a clean end to end rule suggestion that would resolve my requirement

{
"update": {
"issuelinks": [
{
"remove": {
"type": {
"name": "Cloners"
},
"inwardIssue": {
"key": "{{#issue.issuelinks}}{{inwardIssue.key}}{{/issue.issuelinks}}"
}
}
}
]
}
}

[Yogesh Mude]

@orla_mears I have not yet tried but i see there is an action callled Delete issue links in the jira automation and here you can mention the link type as well. so can you please try with this once.