Clone Operation using Jira Automation

Question

Within a Jira Automation for Data Center when using the Clone Operation which fields are cloned by default?

I observed that for Custom fields they do not clone by default unless they are specified in the Additional fields under more Options, however I wondered if anyone can confirm how we can tell which fields are cloned by default and which ones are not using Jira Clone issue operation.

Is it as simple as Custom Fields are not cloned by default and all other Fields are cloned?

Bill Sheboy · Answer

Hi @Robert J Thielen -- Welcome to the Atlassian Community!

In the Jira Data Center documentation for the clone issue action, it states it tries to copy all fields it can, although it does not specify what "fields it can" means: https://confluence.atlassian.com/automation/jira-automation-actions-993924834.html#Jiraautomationactions-cloneissueCloneissue

As this feature appears to be implemented by application code to create the new issue and copy over fields, and not with any non-existent "Clone Issue" REST API, I suspect experimentation is required to confirm what can be copied.

Kind regards,
Bill

Jim Knepley - ReleaseTEAM · Answer

Welcome to the community, @Robert J Thielen

You're correct, custom fields are not cloned by default.

From https://support.atlassian.com/jira-software-cloud/docs/clone-an-issue/

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

* Attachments

* Subtasks

* Links

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