What is copied while cloning an issue

[Asier Vadillo]

Hi everyone!

My question is the title, what is copied when doing a clone for an issue. We need to define some custom fields to not be copied while cloning in our project.

All the info in the community points towards that being not possible without plugins or a rule that change the issue once the clone it is done. 

But then, the only official documentation I could find about cloning in Jira cloud:
https://support.atlassian.com/jira-software-cloud/docs/clone-an-issue/ 

Says : 

"In the cloning process, some information from the original work item isn’t automatically cloned but can be included:

• Custom fields (if they’re set up to be cloned)

"

Which I do not understand. My custom fields are copied, I do not seem to be able to set up if the custom fields are or not cloned and also says the contrary of what it is said in the community.

Anyone has any insight about it? Any way to define fields to not be cloned without plugins/automation rules?

Thanks beforehand!!

[Clara Belin-Brosseau_Elements]

Hi @Asier Vadillo

You’re correct, Jira’s native clone feature is quite limited when it comes to controlling which fields are copied.

When you clone an issue using the built-in feature, Jira will copy:

• Summary, description, components, labels, and most system fields

• Custom fields (if they are standard Jira types)

But it can’t exclude individual fields or custom fields from being cloned.
There’s no configuration in Jira Cloud that lets you choose which fields to include or not.

If you need more flexibility I can suggest giving a try to our app Elements Copy & Sync as it offers full control over the cloning process.

Here’s how you can set it up step by step 👇

1. Create a new recipe

• Go to Elements Copy & Sync → Create a new recipe.

• Select Copy and synchronize Jira work items.

• Define the source and target projects and work item types for your cloning

2. Select what to copy

• In the Content tab, choose exactly which fields you want to copy:

• You can also decide if you want to copy comments, attachments, and issue links.

• If needed, you can even synchronize the work items between the source and clone.

3. Set automation or trigger options

• Configure when the clone should be created:

  • Manually with a button in the issue view, or

  • Automatically on transition, using a workflow post-function or automation.

You can try the app for free for 30 days (and it stays free under 10 users)

I hope this helps :) 

[Marc -Devoteam-]

Hi @Asier Vadillo 

This sentence on the custom field relates to the context of the custom field.

If you have a custom field related to a specific project and to clone an issue to another project, that is not set in the custom field context, this field will not be cloned.

So to do what you want, you need to adjust the custom field contexts and then clone the issue to another project where these fields are not available, then move them back to your project.

A clone within a project will clone all fields on the cloned issue, this can't be set

To achieve what you want, to clone an issue without "some" custom field, you will need a 3rd party solution.

[Jack Brickey]

Good point Marc. I was assuming hear that he is cloning within the same context, but that may not be the case.

[Luka Hummel - codefortynine]

Hi @Asier Vadillo

By default, Jira’s built-in clone function will copy most fields, including custom fields, but does not provide a way to exclude specific fields from being cloned. There is no native setting in Jira Cloud to define which custom fields should or should not be cloned.

If you need more granular control over what gets cloned, including the ability to exclude specific custom fields, you can try our app Deep Clone for Jira. Deep Clone allows you to:

• Clone single issues, bulk clone, or even clone entire projects.

• Map custom fields between projects, even across company-managed and team-managed projects (as long as the field names match).
• Exclude fields from cloning by clearing them in the Field Editor.

[Jack Brickey]

Hi @Asier Vadillo , there is no out-of-the-box setting in Jira Cloud to exclude specific custom fields from being cloned. I believe it comes down to what type of custom field is closed. However, I have not done extensive testing on this. What I would suggest that you do is to create an automation rule, that clones an issue and clones only those fields that are desired.