Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Yes. In Jira Cloud, open the work item, select More options (the three-dot menu), then choose Clone. Jira creates a separate work item, but the clone may not include every comment, field, attachment, or relationship automatically. Review the clone dialog and check the new item before relying on it.
How to clone a Jira ticket
-
Open the work item you want to duplicate.
-
Select More options (the three-dot menu), then choose Clone.
As an Amazon Associate I earn from qualifying purchases.
-
Review the summary. Jira may add a “Clone” prefix, which you can edit.
Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy. -
Change the assignee or reporter if needed, and select any optional content shown in the dialog, such as attachments, subtasks, links, custom fields, comments, or child work items.
-
Select Clone, then open the new work item and verify its fields and relationships.
Atlassian notes that changes to the Jira Cloud work-item experience are rolling out as an open beta, so the menu and available options can differ between sites. Follow the choices visible in your Jira site. Atlassian’s clone guide describes the current Cloud workflow.
What a Jira clone is—and how it relates to the original
Atlassian Support says, “Cloned work items exist as a separate entity to the original work item.” In practice, you can edit the clone independently without changing the original. The current Jira Cloud guide says the items are linked when cloned and can be unlinked later; Jira Work Management documentation describes linking as possible but not mandatory. Check the relationship on the resulting work item rather than assuming it is always present. Jira Cloud clone guide · Jira Work Management 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 errorsWhat Jira copies—and what you should verify
Jira Cloud copies most work-item information, including the summary and description. Depending on the dialog and configuration, you may be able to include attachments, subtasks, links, custom fields configured for cloning, comments, and child work items for Epics. Inspect the available selections rather than assuming every type of content transfers.
Jira Work Management guidance describes additional behavior: summary, affected versions, and components are copied, while time logged, comments, history, and Confluence page links are not. It also says the clone returns to the first step of the corresponding workflow and resolutions are cleared. Those details are specific to that guidance and may not describe every current Jira experience, so check the clone and its resulting status. Jira Work Management guidance
Comments are a common exception
Atlassian’s Cloud support page says comments are not copied by default. It documents an Automation workaround that can copy internal and public comments, but warns that notifications may be triggered. Before enabling such a rule, administrators should confirm which comments are visible to which users and assess the notification impact. Atlassian’s comment-copy guidance
Rank #2
Custom fields across team-managed projects
A normal clone should not be treated as a guarantee that custom-field values will map between projects. Atlassian says direct moves across team-managed projects may fail to preserve those values; its documented workaround is to use Jira Automation to clone into the destination project and map source values to destination fields. That requires a configured workflow. Atlassian’s cross-project guidance
Free tools Windows power users keep installed
One-click scans. No signup required.
Cloning one ticket versus setting up a repeatable copy
| Need | Best-fit approach | Important check |
|---|---|---|
| Duplicate one work item, typically within the same project | Use the built-in More options > Clone action. | Review the clone dialog and verify the result. |
| Copy content beyond the defaults | Use the optional selections in the clone dialog where available; use Automation when a configured rule is needed. | Comments, time logged, history, and other content may not transfer as expected. |
| Clone into another team-managed project while preserving custom-field values | Configure Jira Automation to clone to the destination and map the fields. | Source and destination fields need deliberate mapping. |
| Repeat the same copying process reliably | Consider Jira Automation rather than manually cloning each time. | Test what is copied and review visibility and notification effects. |
What permission do you need to clone a Jira issue?
Atlassian’s Jira Cloud clone guide lists the Create work items space permission as a requirement. Atlassian’s support article says there is no separate reliable “Clone permission”; workflow properties sometimes used to restrict cloning are treated as Create permission properties and can produce inconsistent or unintended effects. Clone guide · Atlassian’s permission guidance
If Clone is missing or the new ticket fails to appear
-
Check whether your account has the required Create work items permission.
-
Review project and workflow configuration, including required fields and validators that may block creation.
-
Check whether the clone dialog offers the content you expect, then inspect the new work item for missing fields or relationships.
Recommended: PC Feels Slow? A Free Scan Shows What's Dragging Windows Down →Recommended: Update Every Outdated Driver on Your PC in One Scan - Free →Recommended: Fix Windows Errors and Clear Junk Files in Minutes - Free Scan →Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy. -
If a configured restriction seems to hide or block cloning, have a Jira administrator review the Create permission and workflow properties. Atlassian documents a Data Center case where workflow validators prevented a cloned issue from being created; the exact cause can depend on the site’s configuration.
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.




