Cloning a Jira Ticket: Step-by-Step Guide and Checklist
Need to reuse an issue without stale details? Get a step-by-step guide to cloning Jira tickets, plus a practical checklist. Read now.
Need to reuse a Jira issue without rebuilding it from scratch? Cloning can save time, but a careless copy may carry stale details, confuse ownership, or leave key fields blank.
That’s frustrating when a teammate acts on the wrong deadline or duplicates work because the new issue still points to an old sprint. The good news: you can clone a ticket in a few steps, then check what carried over before anyone starts work. I’ll walk you through the process, explain what to review, and share a practical checklist for cleaner copies. But here's the truth: cloning is only useful when the new issue reflects the work ahead, not just the details behind it.
How to Clone a Jira Ticket: Step-by-Step
Open the issue you want to reuse, choose the clone action, review the fields, and create the new issue. Then confirm its details and links before assigning work.
Open the original issue. Check that you have the right ticket and that its details are current enough to reuse. Note any fields that should change in the new issue.
Open the issue actions menu. In Jira, look for the actions menu, often shown as three dots, and select Clone. The exact menu placement can vary by Jira version and configuration.
Review the clone form. Jira may let you edit the summary, project, issue type, and other fields before creating the copy. Remove wording that refers only to the original task.
Choose which related details to carry over. If the form offers options for attachments, subtasks, or links, select only what the new issue needs. Options vary across Jira setups.
Create the new issue. Submit the form and wait for Jira to create a separate issue with its own issue key. The original ticket remains in place.
Check the new ticket. Review its summary, description, dates, assignee, status, links, and any copied subtasks. Update or remove anything that does not apply to the new work.
Here's why the final check matters: cloning saves setup time, but it does not decide whether inherited details are still accurate. For example, a copied deadline can make a new task appear overdue before anyone begins.

When Cloning Is Better Than Creating a New Issue
Clone a ticket when the new work follows a proven pattern and needs many of the same fields or steps. A recurring release check, a standard bug investigation, or a familiar onboarding task can be a good fit.
Creating a fresh issue is usually clearer when the work only shares a title or a broad theme with an older ticket. For example, a new feature request should not inherit an unrelated bug’s acceptance criteria simply because both involve the same screen.
You might be wondering: should you clone a ticket that already has a useful checklist? Yes, if those steps still apply. If the new task has a different outcome, keep the useful structure and rewrite the details before assigning it.
What Jira May Copy—and What You Should Verify
A Jira clone generally creates a new issue and can carry over selected issue details. Which fields and related items come across depends on the Jira version, project settings, and options shown during cloning.
| Item | What to check |
| Summary and description | Replace old names, dates, and task-specific instructions. |
| Assignee and reporter | Confirm the right people own or requested the new work. |
| Dates and sprint | Set deadlines and sprint placement for the current plan. |
| Labels and components | Keep only classifications that fit the new issue. |
| Attachments and subtasks | Check whether they were copied and whether each item is still relevant. |
| Comments and work logs | Review whether they carried over; don’t assume the history is identical. |
| Issue links | Confirm the new issue has the intended relationship to the original. |
The new issue gets its own key, even when it resembles the original. Jira may also add a relationship indicating that one issue was cloned from another. Check the link so teammates can understand why the issues are connected.
Let me explain with a release example: cloning last month’s deployment task may preserve a useful checklist, but its old release date and sprint could mislead the team. Keep the steps; refresh the schedule.
Checklist Before You Create the Clone
Use this short checklist before submitting the clone form. It helps you avoid carrying unnecessary details into work that should stand on its own.
Confirm the original ticket is the right model for the new task.
Rewrite the summary so it clearly describes the new work.
Remove old dates, sprint details, and completion notes.
Review the assignee, reporter, priority, and issue type.
Keep only relevant labels, components, links, and attachments.
Decide whether any subtasks should be copied or recreated.
Check that the description and acceptance criteria fit the new outcome.
The best part? A quick review usually takes less time than fixing a misleading issue after work has started. For a recurring workflow, agree on which fields teams should refresh every time.
After Cloning: Verify, Assign, and Communicate
Once the new issue exists, review it as if you had never seen the original. Confirm that its title, scope, ownership, and dates make sense on their own.
Then check its relationship to the original ticket. A visible clone link can help teammates trace the shared context without assuming the two issues have the same status or priority.
For example, a team cloning a bug ticket for a second browser may keep the reproduction steps, but should update the affected browser, test results, and owner. A short comment can explain why the new issue exists and what differs.
If the cloned issue includes subtasks, review each one before assigning it. A copied checklist can be useful, but an obsolete step can turn into unnecessary work or an inaccurate progress signal.
Project Management for Repeatable Ticket Work: ONES.com

Value Proposition
When teams repeatedly clone Jira tickets, the broader challenge is keeping workflows, fields, and project knowledge consistent. ONES.com brings project management and knowledge management together, with ONES Project as a Jira alternative and ONES Wiki as a Confluence alternative; each is sold separately.
Core Capabilities
Complex workflows: When a repeated task moves through several review stages, Jira-compatible workflows in ONES Project help teams map the process and keep each transition visible.
Different project needs: When one team needs fields that another does not, custom workflows and fields let teams shape issue tracking around their work.
Sprint planning: When copied work needs a fresh place in the delivery plan, sprint management helps teams organize the work around current iterations.
Routine task handling: When teams repeat the same administrative actions, automation can reduce manual steps and help keep workflows consistent.
Progress visibility: When cloned issues make status harder to follow, built-in reporting helps teams review progress without relying on extra reporting plugins.
Project and team knowledge: When issue details need shared guidance, ONES Wiki provides knowledge management alongside the separately sold ONES Project.
Deployment requirements: When teams need a particular hosting arrangement, ONES.com offers Cloud, On-Premise, Private Cloud, and Air-gapped deployments.
Self-hosted feature needs: When teams need to run the platform in their own environment, ONES.com provides feature parity between cloud and self-hosted versions.
Application Scenarios
A product team handling recurring release checks could use ONES Project to organize work with its workflow, sprint management, custom fields, and reporting. The team can define which details need refreshing for each release instead of treating every copied issue as ready without review.
A company with restricted network requirements may consider an On-Premise, Private Cloud, or Air-gapped deployment. Teams can evaluate the deployment that fits their environment while using project management capabilities designed for structured issue workflows.
ONES.com offers a free plan for up to 30 seats. Teams comparing platforms can assess its workflows, reporting, deployment options, and reduced reliance on plugins against their project requirements.
Common Challenges When Cloning Jira Issues
Old details appear in the new ticket. Dates, names, and acceptance criteria can become inaccurate. Review the summary and description before assigning the issue.
The clone gets mistaken for the original. Similar titles can blur ownership. Add a clear qualifier, such as the product area or release, and check the issue link.
Unneeded subtasks create extra work. A copied task list may include steps that no longer apply. Remove or revise subtasks before anyone starts them.
Team members expect comments or work logs to carry over. Jira behavior can vary by configuration. Check the new issue directly, and add relevant context rather than assuming its history matches.
Copied work lands in the wrong sprint. Review sprint and due-date fields after creation. Set them according to the current plan, not the original ticket’s schedule.
FAQs About Cloning Jira Tickets
Does cloning a Jira ticket change the original issue?
No. Cloning creates a separate issue with its own issue key, while the original remains in Jira. You can update the clone without changing the original ticket. Still, review any links between them so teammates can distinguish their relationship and understand which issue owns the new work.
Will a Jira clone copy comments and attachments?
It depends on the Jira setup and the options available during cloning. Inspect the clone form for attachment or related-item settings, then check the created issue. Comments and work logs may not carry over in the same way as issue fields, so add any context the new task genuinely needs.
Can I clone a Jira issue into another project?
Some Jira configurations allow you to choose a different project or issue type during the clone process. Availability depends on your Jira setup and permissions. If the option appears, confirm that the destination project supports the required fields and issue type before creating the new ticket.
Why can’t I see the Clone option in Jira?
The option may be hidden by your permissions, project configuration, or the Jira interface in use. Ask a Jira administrator to check your project access and available issue actions. If cloning is unavailable, you can create a new issue and manually carry over only the details that still apply.
Conclusion
Cloning a Jira ticket is straightforward: open the issue, choose Clone, review the available options, create the new issue, and verify its details. The important step is deciding what the new work should inherit.
Stale fields and unnecessary subtasks can turn a time-saving copy into a source of confusion. Check the schedule, ownership, description, links, and related items before work begins. With that habit, you can reuse a proven structure while giving each new issue the context it needs.