How to Clone an Issue in Jira: Steps and Common Pitfalls
Need to clone issue in Jira without missing key details? Follow the steps, avoid common pitfalls, and review your copy—read now.
Need a Jira issue for a second team, release, or environment? Recreating it by hand can take time and leave out important details, like attachments, labels, or acceptance criteria. Copying the wrong fields can create confusion, too, especially when the new issue should be tracked separately from the original.
You can clone an issue directly in Jira, then review the copy before anyone acts on it. Jira gives the new issue its own key and can link it to the original, while options in the clone dialog let you control what carries over. Here’s how to clone an issue in Jira, what to check before confirming, and how to avoid common pitfalls such as duplicate work, unexpected notifications, and misplaced sprint assignments.
How to Clone an Issue in Jira
To clone an issue in Jira, open the issue, choose More or the actions menu, select Clone, review the fields and clone options, then create the new issue. Jira assigns the copy a new issue key. Depending on your Jira version and settings, the clone dialog may offer options for attachments, links, subtasks, or other details.
- Open the issue you want to copy. Check that you have the correct project and issue key. Review the summary and description before cloning.
- Open the issue actions. In Jira Cloud, select More near the top of the issue. In other Jira versions, the option may appear in an actions menu.
- Select Clone. Jira opens a dialog where you can set details for the new issue. If you cannot see Clone, your permissions, project configuration, or Jira version may affect its availability.
- Edit the summary and other fields. Jira may add a “CLONE -” prefix to the summary. Change it to describe the new work, and review fields such as project, issue type, priority, assignee, and labels.
- Choose what to carry over. Review the available checkboxes for attachments, issue links, or subtasks. Options can vary, so do not assume Jira will copy every related item.
- Confirm the clone. Select the button to create the issue. Jira should display the new issue key when the process succeeds.
- Check the new issue. Open it and verify its fields, links, and included content. Make sure it belongs in the intended project or workflow before moving it forward.
For example, if you need a similar bug report for a second product, update the summary, project, affected version, and reproduction details. Keep a link to the original only if the relationship will help the team.

What Jira Copies and What You Should Verify
A clone is a separate Jira issue, not a live duplicate. Changes to the new issue do not automatically update the original, and updates to the original do not automatically appear in the clone.
Jira generally carries over many issue details, but the exact fields and optional content depend on the clone dialog and your configuration. Treat the dialog as the guide to what will be included. After cloning, check key details such as the description, priority, components, labels, assignee, and due date.
Comments, work logs, and other activity history may not carry over as you expect. Attachments, issue links, and subtasks may have separate options. If a detail matters to the work, verify it directly instead of assuming the clone includes it.
Here’s why: a copied due date or assignee can make a fresh task look ready when it is not. For a release-specific bug, for instance, confirm the affected version and sprint rather than carrying over old values without review.
When Cloning Is Useful—and When It Is Not
Cloning works well when a new issue needs much of the same structure as an existing one. You might clone a recurring maintenance task, create a related bug for another product, or start a new task with the same acceptance criteria.
It can also help when teams use a consistent issue template but do not have a dedicated template feature configured. A cloned issue can provide a useful starting point, as long as you replace details that apply only to the earlier work.
But here's the truth: cloning is not the right choice for every repeat task. If you need the same work created on a schedule, a recurring-task workflow or automation may be easier to maintain. If you only need to assign the existing work to someone else, changing the original issue is usually clearer.
Ask yourself whether the new work needs its own status, owner, and history. If yes, cloning may fit. If the team needs one shared record, update or link the existing issue instead.
Common Pitfalls to Avoid After Cloning
Most cloning problems happen after the new issue is created. A quick review helps prevent copied details from sending work to the wrong team or making two issues appear to represent one task.
- Leaving a vague “CLONE” summary: Replace the prefix with a clear description, such as “Update checkout error handling for mobile.”
- Keeping outdated ownership: Check the assignee and team fields. The person assigned to the original may not own the new work.
- Carrying over the wrong sprint or release: Confirm the target sprint, version, and due date. Old scheduling details can mislead dashboards and planning meetings.
- Creating confusing links: Keep the clone relationship when it explains why the issues are connected. Remove or avoid extra links that imply the new work is a duplicate.
- Forgetting access and notifications: Check project permissions and watchers. A new issue can notify people or expose details to a different project audience.
The best part? These checks take only a moment. Open the new issue, compare its important fields with the intended work, then confirm the status and project are correct.
Project Workflow Management with ONES.com
If cloning is one part of a wider project workflow, ONES.com offers a project management platform through ONES Project, a Jira alternative. ONES Project is sold separately from ONES Wiki, its knowledge management product.

ONES Project supports teams that want to manage tasks, sprints, and workflows in one project environment. It offers Jira-compatible workflows, built-in reporting, custom workflows and fields, sprint management, and automation. Cloud and self-hosted deployments have feature parity, including On-Premise, Private Cloud, and air-gapped options. The free plan supports up to 30 seats.
Where ONES Project Can Help
- Teams need to repeat issue workflows: Custom workflows and fields let teams represent their own review and delivery steps, reducing reliance on extra plugins.
- Sprint planning needs clearer oversight: Sprint management helps teams organize planned work and follow progress through a cycle.
- Project status is hard to track: Built-in reporting gives teams a way to review progress without assembling updates from separate tools.
- Manual handoffs slow recurring work: Automation can handle routine transitions and actions, leaving people to review exceptions.
- Jira-compatible processes matter: Jira-compatible workflows can help teams preserve familiar ways of working while evaluating a Jira alternative.
- Plugin maintenance is becoming burdensome: Native workflow and reporting capabilities can reduce the need to add plugins for common project needs.
- Hosting requirements limit options: Teams can choose Cloud, On-Premise, Private Cloud, or air-gapped deployment to match their environment.
- Project and knowledge work need different spaces: Teams can use ONES Project for project management and ONES Wiki for knowledge management, with each sold separately.
Practical Scenarios
A software team can use ONES Project to plan sprint work, automate routine workflow steps, and review progress through built-in reports. When a recurring bug needs a new issue, the team can create a separate work item and check its ownership and sprint placement.
A company with restricted network requirements can consider a self-hosted deployment, including an air-gapped environment. That lets its project team manage custom workflows and fields without relying on a cloud deployment.
Let me explain: ONES Project is worth evaluating when your concern extends beyond a single Jira clone. Compare workflow fit, deployment needs, reporting, and plugin requirements before deciding whether it suits your team.
Common Challenges
The Clone Option Is Missing
Problem: You open an issue but cannot find Clone in the actions menu.
Solution: Check your project permissions and ask a Jira administrator whether the issue type or project configuration affects cloning. Menu placement can also differ across Jira versions.
The New Issue Has the Wrong Details
Problem: The clone carries over an old assignee, release, due date, or other field that does not fit the new task.
Solution: Review the clone dialog before confirming, then verify the new issue afterward. Update any copied values that do not apply.
Related Work Is Missing
Problem: An attachment, subtask, or issue link does not appear on the clone.
Solution: Check the optional clone settings before creation. If Jira does not offer the setting you need, add or recreate the relevant item manually and confirm the relationship.
The Team Treats Both Issues as One
Problem: The original and clone have similar summaries, so teammates update the wrong issue or assume progress is shared.
Solution: Give the new issue a specific summary, retain a meaningful clone link, and state the difference in the description. Remind the team that each issue has its own status and history.
FAQs
Does cloning a Jira issue duplicate the original issue?
Cloning creates a new issue with its own key and workflow history. It does not turn the original and new issues into one shared record. Depending on the options available, Jira can also create a link that shows the relationship between them. Changes made to one issue generally do not update the other, so manage each issue separately.
Can I clone an issue into another Jira project?
Jira features and project settings can affect which fields you can change during cloning. Review the project and issue type choices in the clone dialog. If you cannot select the destination project, check your permissions or ask a Jira administrator about the available workflow. After creation, verify that the new issue is in the correct project.
Will Jira copy comments and attachments when I clone an issue?
Do not assume every comment or attachment will carry over. The available clone options vary, and attachments may have their own setting. Comments and work logs may not be included as part of the clone. Review the dialog, then check the new issue. If a specific attachment or context is essential, confirm that it appears or add it separately.
Can I clone an issue with its subtasks?
Some Jira clone dialogs offer an option to clone subtasks, while availability can vary with your Jira version and configuration. Look for that option before confirming. If you do not see it, create the required subtasks separately and link them appropriately. Check that each new subtask has the right summary, owner, and schedule.
Conclusion
Cloning in Jira is a practical way to create a separate issue with much of an existing issue’s structure. Open the issue, use the Clone action, review the available options, and check the new issue before work begins.
That final review is what prevents copied assignments, dates, or links from creating avoidable confusion. When your needs involve broader workflow design, reporting, or deployment choices, you can also evaluate ONES Project as a Jira alternative. Choose the approach that gives each piece of work clear ownership and its own accurate history.