nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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!

Accepted answers

All comments

Yogesh Mude_f9cg0f

@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}}"
}
}
}
]
}
}

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

Screenshot 2025-08-06 at 13.01.39.png

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_f9cg0f

@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.

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.

2025-08-07 17-41.png

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.

orla_mears

@Luka Hummel - codefortynine thanks for the suggestion - unfortunately it's just a small one off request so wouldn't justify adding on a paid 3rd party app but the feature set looks good!

Clara Belin-Brosseau_Elevatic

Hi @orla_mears

If you need to clone a work item without linking the original and cloned one, I can recommend trying our app Elements Copy & Sync.

Cloned actions can be triggered with Automation or with post-functions.

The app is for free during 30 days (and it stays free under 10 users), so don't hesitate to give it a try!

orla_mears

HI @Clara Belin-Brosseau_Elements thanks but don't have budget for an add on solution.

I ended up disabling the top level admin setting that flagged cloned issues as such, and it's working fine, it just means that no issues that I clone can ever be identified as a clone, all will just look like brand new work items.

Clara Belin-Brosseau_Elevatic

Alright @orla_mears

Noted

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management