How to Clone an Issue in Jira: Steps and Best Practices
Need a Jira duplicate without cleanup headaches? Learn the steps and best practices for cloning an issue in Jira. Read now to get started.
Need a second Jira issue with the same setup, but worried you’ll miss a field or copy more than you intended? A rushed duplicate can create extra cleanup, confuse ownership, and leave your team unsure which issue to update.
Cloning gives you a head start by creating a separate issue with selected details carried over. The key is knowing where Jira places the action, checking what the clone includes, and adjusting its summary and ownership before you move on. Here’s how to clone an issue in Jira, what to review afterward, and how to avoid common mistakes.
How to clone an issue in Jira
Open the issue you want to copy, choose More (or the three-dot menu), select Clone, review the available options, and create the new issue. Jira’s menus and clone settings can vary by product version, project configuration, and permissions.
- Open the issue. Find the Jira issue you want to use as a starting point. Check that it has the right issue type and details for the work you’re planning.
- Choose the clone action. Open More or the three-dot menu on the issue. Select Clone. If the action is missing, you may lack permission, or your Jira setup may use a different menu arrangement.
- Review the clone form. Jira may let you edit the new issue’s summary and choose whether to copy items such as subtasks, attachments, or links. Available choices depend on your Jira version and configuration.
- Give the new issue a distinct summary. Replace a generic title with one that identifies the new work. For example, change “Update payment error handling” to “Update payment error handling for mobile checkout.”
- Check any project or field settings shown. Review the fields Jira presents, including any required custom fields. Keep only the details that make sense for the new issue.
- Create the clone. Submit the form, then open the new issue. Check its issue key and confirm it is separate from the original.
- Review ownership and relationships. Confirm the assignee, due date, priority, labels, links, and subtasks. Update anything that should differ, then tell collaborators which issue they should use.
But here's the truth: a clone is a starting point, not a finished task. A quick review after creation helps prevent old ownership, stale dates, or irrelevant links from following the new issue.

What Jira cloning carries over
Cloning creates a new issue using details from an existing one. Jira commonly carries over fields such as the summary, description, and issue type, while the exact set can depend on your configuration and clone options.
Some Jira setups offer choices for copying subtasks, attachments, or issue links. Comments and work logs may not be copied by default. Check the clone form and the resulting issue rather than assuming every detail transfers.
Here's why: the new issue has its own key and can be managed separately. For example, cloning “Prepare launch checklist” might preserve its description while giving a second team a new issue to own.
Best practices before and after you clone
Use cloning when you need a repeatable starting point, such as a recurring release task or a similar bug report. Before creating the clone, make sure the original issue is a useful model rather than a one-off task full of outdated context.
- Make the title specific. Add the product area, release, team, or other detail that distinguishes the new work.
- Refresh dates and ownership. A previous assignee or due date may no longer fit the new task.
- Review descriptions and custom fields. Remove old instructions, environments, or values that don’t apply.
- Check subtasks and links. Keep relationships that support the new work; remove ones that point to an unrelated effort.
- Confirm the issue type and project. A copied task may need a different type or destination to follow the correct workflow.
- Tell collaborators what changed. A brief note can prevent someone from updating the original by mistake.
The best part? A short review makes cloning more reliable without turning it into a long administrative task. For example, a team can reuse a release checklist and still update the release name, owner, and target date before work begins.
When cloning is the right choice
Cloning works well when a new issue needs much of the same structure as an existing one. A support team might duplicate a well-defined bug report for a similar error, then update the affected version and reproduction steps.
For repeated work, cloning can preserve a useful description and field setup. It can also help teams follow a consistent pattern when the same kind of task appears across releases or product areas.
Use a different approach when the new work is only a small addition to the original task. A comment or subtask may be clearer than creating another full issue. If the goal is to repeat a process regularly, consider whether a Jira template or automation fits better than manual cloning.
Let me explain: the right choice depends on whether the work is genuinely separate. If two teams need different owners, deadlines, or progress tracking, separate issues make that distinction easier to see.
Verify the clone and keep the work clear
After creation, compare the new issue with the original. Check the summary, description, assignee, priority, due date, labels, custom fields, subtasks, attachments, and links that matter to your workflow.
Look for details that can cause confusion later. A cloned issue with the old release name or a link to an unrelated incident may appear complete while pointing the team in the wrong direction.
Then confirm the clone has its own issue key and that the relationship to the original is understandable. If your Jira setup displays a clone link, use it to help teammates navigate between the two issues.
You might be wondering: does creating a clone change the original? The clone is a separate issue, so edits to one generally don’t update the other automatically. Check any links or automation rules configured by your Jira administrator.
Issue management with ONES.com
ONES.com combines project management and knowledge management in one platform. ONES Project supports issue and project workflows, while ONES Wiki provides a knowledge base; the products are sold separately.

If your team is reviewing ways to manage Jira-style work, ONES Project is a Jira alternative with Jira-compatible workflows. It supports custom workflows and fields, sprint management, automation, and built-in reporting. Cloud and self-hosted deployments offer full feature parity.
Core capabilities
- Repeated work is hard to track → Use custom workflows and fields in ONES Project → Result: Capture the details and stages your team needs for recurring tasks.
- Sprint work needs a clear structure → Use sprint management → Result: Organize issues around planned development cycles.
- Routine actions take extra effort → Use automation → Result: Reduce repetitive steps in supported workflows.
- Progress is difficult to review → Use built-in reporting → Result: Give teams a view of project activity and status.
- Teams rely on added plugins → Review the platform’s native capabilities → Result: Reduce plugin reliance when the required functions are already included.
- Jira workflows are familiar to the team → Use Jira-compatible workflows → Result: Keep a recognizable way of handling issues while evaluating an alternative.
- Work must run in a restricted environment → Choose Cloud, On-Premise, Private Cloud, or Air-gapped deployment → Result: Match deployment to your organization’s operating requirements.
- Teams need project work and shared guidance → Pair ONES Project with ONES Wiki → Result: Manage project activity and knowledge through products in the ONES.com platform.
ONES.com offers a free plan for up to 30 seats. Its deployment options include Cloud and self-hosted environments, with full feature parity between cloud and self-hosted versions.
Application scenarios
Recurring engineering tasks: A team can use custom workflows and fields to shape repeated issue work, then review progress through built-in reporting.
Restricted-network project management: An organization that needs an air-gapped deployment can evaluate ONES Project for issue workflows in that environment.
Project work with team guidance: A team can manage issues in ONES Project and maintain shared knowledge in ONES Wiki, selecting each product to fit its needs.
Common challenges when cloning Jira issues
- The clone option is missing. You may lack the required permission, or the menu may differ in your Jira version. Ask a Jira administrator to check your access and project settings.
- The new issue contains outdated details. Old dates, labels, owners, or descriptions can slip through. Review the clone immediately and update fields before assigning work.
- Subtasks or links are missing. Clone options may control whether these are copied. Check the available settings, then add relevant relationships to the new issue if needed.
- Teammates update the wrong issue. Similar titles can make two issues hard to distinguish. Give the clone a specific summary and share its new issue key.
- A clone is created when only a small update was needed. Extra issues can scatter discussion and progress. Use a comment or subtask when the work belongs within the original issue.
FAQs about cloning Jira issues
Does cloning a Jira issue copy its comments?
Comments may not be copied when you clone an issue. What transfers depends on your Jira version, clone options, and project configuration. Open the new issue after cloning and check whether any discussion needed for the new work is available. If context matters, add a concise note or link to the relevant conversation.
Can I clone an issue into a different Jira project?
Options vary by Jira product and configuration. Some workflows may allow a destination project or provide another way to move or recreate an issue. If you don’t see a destination choice during cloning, check with your Jira administrator about the permitted process. Afterward, verify the issue type and required fields in the destination project.
Will changes to the original update the clone?
Cloning creates a separate issue, so edits to the original generally don’t update the clone automatically. A link between the issues can help your team see their relationship, but it does not necessarily synchronize their fields. Check any Jira automation configured for your project if you expect particular updates to carry across.
Can I clone a Jira issue with its subtasks?
Some Jira clone forms provide an option to include subtasks. If that choice appears, review the subtasks before creating the clone. Their summaries, owners, or dates may need changes for the new task. If the option isn’t available, ask your Jira administrator what alternatives your setup supports.
Conclusion
Cloning an issue in Jira can give you a useful head start when a new task shares details with an existing one. Open the issue, choose More and Clone, review the options, and create a distinct summary.
Then check ownership, dates, fields, subtasks, and links before work begins. That small review helps prevent the confusion that makes duplicate issues costly. When the work is genuinely separate, a carefully updated clone gives your team a clearer place to plan and track it.