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!!

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

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