iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Yes. Jira Cloud’s Clone action creates a separate work item based on an existing ticket. It can copy most of the original’s information, but comments, attachments, subtasks, links, and other details may depend on options in the clone dialog or on your site’s configuration. Review the choices and the resulting ticket rather than assuming everything transferred.
How to clone a Jira ticket
-
Open the work item you want to duplicate.
-
Select More options (the three-dot menu), then choose Clone.
-
Review and edit the summary. Jira may add a “Clone” prefix automatically.
Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy. -
Change the assignee or reporter if the new ticket should have different people.
#1 Best Overall
-
Review any optional content choices shown, such as attachments, subtasks, links, custom fields, comments, or an Epic’s child work items.
-
Select Clone, then inspect the newly created work item and its relationship to the original.
Atlassian says changes to the Jira Cloud work-item experience are rolling out as an open beta, so the menu and available options may differ between sites. Use the controls shown in your Jira instance. Atlassian’s Jira Cloud cloning guide
Recommended Free Tools
What a Jira clone is—and whether it stays linked
Atlassian Support describes the result this way: “Cloned work items exist as a separate entity to the original work item.” In practical terms, the clone is a new ticket you can edit independently; changes to one do not make it the same item as the other.
The current Jira Cloud guide says cloned items are linked and can be unlinked later. Jira Work Management guidance describes linking as possible, rather than automatic in every case. Check the issue links on the created ticket to confirm what your site did. Jira Cloud cloning guide · Jira Work Management cloning guidance
What information does Jira copy?
Jira Cloud copies most work-item information, including the summary and description. The clone dialog may offer choices for additional content, but the exact options depend on the experience and configuration available on your site. Custom fields, for example, may be available to clone only when configured for it. Atlassian’s Jira Cloud cloning guide
Comments are not copied by default
Do not assume comments will appear on the clone. Atlassian’s Cloud support page says they are not copied by default and documents an Automation workaround. That approach can copy internal as well as public comments, so administrators should verify comment visibility and notification behavior before enabling it; notifications may be triggered. Atlassian’s comment-copying guidance
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsOther details can behave differently
Jira Work Management’s guidance lists summary, affected versions, and components among copied details. It also says time logged, comments, history, and Confluence page links are not cloned, and that status returns to the workflow’s first step while resolutions are cleared. These specifics are from that product guidance; check your current clone dialog and the resulting ticket because behavior can differ across Jira experiences. Jira Work Management cloning guidance
Cloning within a project versus across projects
For an individual duplicate, the built-in Clone action is the direct route. If you need to copy a work item between team-managed projects, do not assume an ordinary clone or move will preserve all custom-field values. Atlassian documents an Automation approach that clones into the destination project and maps source values to destination custom fields. This requires a configured workflow; it is not a guarantee that a standard clone will map every field. Jira Cloud cloning guide · Atlassian’s cross-project custom-field guidance
What permission do you need to clone?
Atlassian’s Jira Cloud cloning guide lists the Create work items space permission as a requirement. Atlassian support also cautions that there is no separate reliable “Clone permission.” Workflow properties sometimes used to restrict cloning are treated as Create permission properties and can cause inconsistent or unintended effects. Jira Cloud cloning guide · Atlassian’s cloning-permissions guidance
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.If Clone is missing or the new ticket fails
-
Ask an administrator to check that you have the Create work items permission for the relevant space or project.
Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy. -
Check required fields and project or workflow configuration that may affect creation.
-
If Clone is visible but creation fails, workflow validators or other configuration may be blocking the new item. Atlassian documents a Jira Data Center case where validators prevent a cloned issue from being created.
-
After a successful clone, inspect its fields, comments, optional content, and issue links to confirm it meets your needs.
Quick Recap
Bestseller No. 1Bestseller No. 3
Atlassian’s cloning-permissions guidance
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
