Cloning an Issue

Clone Issue allows a user to create a duplicate of an issue within the same project. The clone issue is a replica of the original issue, containing the same information stored in the original issue — e.g. Summary, Affects Versions, Components, etc. The clone issue can also be linked to the original issue using a 'clone' link.

A clone issue is a separate entity from the original issue. Operations on the original issue have no affect on the clone issue and vice versa. The only connection takes the form of the link (if created) between the original and the clone issue.

A clone issue retains the following information:

• Summary - with optional prefix (specified in jira-application.properties)
• Description
• Assignee
• Environment
• Priority
• Issue Type
• Security
• Reporter
• Components
• Affects Versions
• Fix For Versions
• Issue Links (optional)
• Attachments (optional)

Details such as time tracking and comments are not cloned.

Creating a Clone Issue

To clone an issue, select the 'Clone' link available in the issue operations menu. It is possible to edit the clone issue summary before creating the clone issue.

• If the issue contains links to other issue(s), you will be prompted to select whether or not to include the links in the new clone issue.
• If the issue contains attachments, you will be prompted to select whether or not to include the attachments in the new clone issue.

Clone Issue Linking

The clone issue can be automatically linked to the original issue when creating the clone issue, using a pre-existing link type.

JIRA queries the jira-application.properties file for the jira.clone.linktype.name setting.

• If this property is unset, JIRA will not create a link between the original and clone issues.
• If this property is set, JIRA will use the pre-existing link type with the specified name as the link type. If a link type with this name does not exist, a link is not created between the original and clone issues.

The link type with the name specified in the properties file should be created before creating clone issues if linking is required.

Clone Issue Summary Prefix

The clone issue summary can be prefixed with a string, e.g. "Clone Issue - ". This string is specified in jira-application.properties with the jira.clone.prefix property and is prefixed to the issue summary.

Cloning and Sub-Tasks

Sub-Tasks can be cloned in the same manner as other issue types.

If the original issue has associated sub-tasks, clone sub-tasks will also be created for the clone issue. However, the clone sub-task summaries will not include the property file specified prefix.