JIRA 4.3 : Cloning an Issue
This page last changed on Mar 13, 2011 by ggaskell.
'Cloning' (copying) an issue allows you to quickly 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 effect on the clone issue and vice versa. The only connection is a link (if created) between the original and the clone issue. A clone issue retains the following information:
Details such as time tracking and comments are not cloned. Creating a Clone IssueTo clone an issue,
Clone Issue LinkingThe 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 linking of clone issues is required, your JIRA administrator should create the link type with the name specified in the properties file before anyone starts creating clone issues. Clone Issue Summary PrefixThe clone issue summary can be prefixed with a string, e.g. "Clone Issue - ". This string is specified by your JIRA administrator in jira-application.properties with the jira.clone.prefix property and is prefixed to the issue summary. The default prefix is 'CLONE - '. Cloning and Sub-TasksSub-Tasks can be cloned in the same manner as other issue types. If the original issue has associated sub-tasks, that issue's sub-tasks will also be cloned. The summary of a cloned sub-task will also include the prefix specified in the properties file. |
![]() |
Document generated by Confluence on Mar 27, 2011 18:26 |