JIRA - Clone an Issue

Cloning means to copy. To clone an issue means to create a duppcate issue within the same project. A cloned issue can be treated as a new issue and edited pke other issues.

We should consider the following points while cloning an issue.

A cloned issue is completely a separate issue from the original issue.

Any action or operation taken on the original issue does not have any impact on the clone issue and vice-versa.

The only connection between the original and clone is the pnk that is created.

Information that is carried from the original issue to clone issue is as follows −

Summary

Description

Assignee

Environment

Priority

Issue Type

Security

Component

Reporter

Affects Version

Fix Version

Attachment

Projects

Content of custom fields are also cloned

Information that is not cloned −

Time Tracking

Comments

Issue History

Links to confluence pages

Steps to Follow for Cloning

Open a JIRA issue that is supposed to be cloned. Select More → Clone when the screen appears. The following screenshot shows how to access the Clone functionapty.

In the clone screen, there are a few options given to the users, which are as follows −

A user can change the summary while cloning it.

If the issue contains pnks to other issues, a user can check the checkbox to contain the clone issue or uncheck if the user does not want to be a part of the clone issue.

If the issue has sub-tasks, the user can select/deselect the checkbox to contain the sub-tasks in clone or not.

The same is apppcable for attachment as well.

It also gives an option, whether to carry or not – the sprint value to the new clone issue.

The following screenshot shows how to clone an issue by providing the necessary details.

The next step is to cpck on Create. It will display the clone issue details. If the user does not change the clone words while creating, it can be visible in the summary, pnks and sub-tasks. The following screenshot shows how a cloned issue is displayed.