How to Clone a Jira Issue: A Step-by-Step Guide for Teams
Need to duplicate work without missing details? This jira issue clone guide shows how to copy an issue and verify fields. Read now to clone with confidence.
Duplicating a Jira issue sounds simple until the new issue misses a key detail, lands in the wrong project, or creates confusion about what work is still open. A rushed copy can leave your team with mismatched priorities, incomplete task details, or two tickets that appear to track the same work.
But here's the truth: cloning works best when you treat it as a fresh issue with useful context, not a perfect replica. Jira creates a new issue, and the fields or relationships carried over can vary with your setup.
Here’s how to clone an issue, check what came across, and keep your team’s work organized. I’ll also show you when cloning makes sense and how to create a reliable team process.
How to Clone a Jira Issue
Open the issue you want to copy, choose the clone action, review the details, and create the new issue. Then check its key fields and relationship to the original.
Open the issue. Find the Jira issue you want to reuse and confirm it contains the details you need. Check the project, issue type, and current status before you start.
Choose the clone action. Open the issue’s actions menu, often shown as an ellipsis or under More, and select Clone. The menu label or location may vary by Jira version and project setup.
Review the new issue’s details. Jira opens a form for the clone. Check its summary, description, project, issue type, and any other fields shown. Jira may add a prefix such as “CLONE -” to the summary; edit it so the new title describes the work clearly.
Choose any available clone options. If Jira offers options such as cloning subtasks, select them only when the new work needs those same smaller tasks. Review any other options shown before continuing.
Create the clone. Submit the form. Jira creates a separate issue with its own issue key. Open it and confirm that it appears in the intended project and has the right details.
Check links and ownership. Review the relationship between the original and new issue, then set the assignee, priority, due date, and other fields that should differ. Confirm the new issue is ready for your team’s workflow.
Here's why the final check matters: a clone is a new issue, and its status or fields may not match the original exactly. Jira configuration and the options available in your project can affect what carries over.

What Jira Cloning Does—and What to Review
Cloning creates a new issue that can reuse useful details from an existing one. Jira assigns the new issue its own key, so the original and clone can be tracked separately.
The issue form and project settings determine which information is carried over. Details such as the summary, description, issue type, priority, labels, components, and custom fields may be available to copy. Review the new issue instead of assuming every field was duplicated.
Some information may be absent or behave differently, including comments, work logs, status, issue links, or attachments. The exact result depends on your Jira version, project configuration, and clone options.
For example, if you clone a bug from one release to track a similar issue in the next release, update the affected version and assignee. Keep the useful reproduction steps, then confirm the new ticket has its own correct relationships.
When to Clone an Issue Instead of Creating One
Cloning is useful when a new task needs much of the same structure as an existing one. A recurring release checklist, a familiar bug report, or a standard support task can provide a practical starting point.
Choose a fresh issue when the new work is substantially different or needs a clean description. Reusing an old issue with several outdated details can take longer than creating a new one from scratch.
You might be wondering: should you clone a parent issue with subtasks? Do so when the same breakdown applies. For a new feature with different work, clone only the parent or create a fresh task structure.
A Reliable Team Process for Cloned Issues
Agree on which issue types your team commonly clones and what should be reviewed after each copy. For example, a support team might reuse a bug report template while updating the customer, environment, and severity.
Give the clone a clear summary before assigning it. A title such as “CLONE - Login failure” may be useful briefly, but a specific title like “Login error on Android after password reset” is easier to scan.
Make ownership explicit. Set the assignee and due date when they apply, and check that the new issue enters the correct project workflow. A cloned issue with an old owner or release target can mislead the team.
The best part? A short review habit catches most copy errors. Ask the person creating the clone to verify its summary, description, owner, priority, status, links, and subtasks before work begins.
Common Problems When Cloning Jira Issues
The clone action is missing. The available actions can depend on your Jira product, project configuration, and permissions. Check that you can create issues in the project, then ask a Jira administrator whether cloning is available in that project.
The new issue has an unexpected status. Jira may create the issue using the project workflow’s starting status. Review the status after creation and move the issue through the approved workflow if needed.
Old details appear in the clone. Reused descriptions, assignees, versions, or dates can be incorrect for new work. Review each field that could change, and replace stale details before assigning the issue.
Subtasks or relationships are missing. Cloning options and project settings affect what is included. Check the new issue’s subtasks and links, then add the relationships required for the work.
ONES.com Solution for Managing Jira-Style Work

Value Proposition
ONES.com brings project management and knowledge management together, with ONES Project for project work and ONES Wiki for team knowledge. ONES Project is a Jira alternative for teams looking to manage issues, workflows, and project reporting in one platform.
Core Capabilities
Issue workflows feel inconsistent: ONES Project supports Jira-compatible workflows, giving teams a familiar way to organize issue lifecycles.
Repeated tasks need clearer handling: Custom workflows and fields let teams represent their own issue details and review stages.
Sprint work is hard to coordinate: Sprint management helps teams plan and track work within iterative development cycles.
Progress is difficult to review: Built-in reporting gives teams a way to monitor project activity without relying on extra reporting add-ons.
Routine work consumes time: Automation can handle selected recurring actions, helping teams reduce manual steps.
Project context is scattered: ONES Wiki provides a knowledge management space alongside project management through ONES.com.
Teams need different hosting arrangements: ONES.com is available in Cloud, On-Premise, Private Cloud, and Air-gapped deployments.
Self-hosted teams worry about feature gaps: ONES.com offers full feature parity between cloud and self-hosted versions, supporting teams with deployment requirements.
ONES Project and ONES Wiki are sold separately. Teams can assess the product that fits their needs, while Jira-compatible workflows and built-in capabilities may reduce reliance on plugins.
Application Scenarios
Development teams standardizing issue work: A team can configure custom fields for recurring bug details, use sprint management for planned work, and apply automation to routine workflow steps.
Organizations with restricted hosting needs: A team that requires an on-premise or air-gapped deployment can evaluate those options while retaining the platform’s feature parity across cloud and self-hosted versions.
FAQs
Does cloning a Jira issue create a separate issue?
Yes. Jira creates a new issue with its own issue key, so the clone can be assigned, updated, and tracked independently. Some details may be reused from the original, depending on the form, project configuration, and options available. Review the new issue after creation, especially its summary, status, owner, and links.
Can I clone an issue into another Jira project?
The available project options depend on your Jira setup, permissions, and product version. If the clone form lets you choose another project, confirm the destination and check that its issue type and required fields are supported. If you cannot select the project, ask a Jira administrator about permissions or use the project’s approved issue-creation process.
Will Jira clone an issue’s comments and attachments?
Do not assume that every comment or attachment will appear in the clone. What Jira carries over can depend on your version, configuration, and the options shown during cloning. After creating the new issue, check whether your team needs any additional context or attachments and add them through your normal process.
Can I clone an issue with its subtasks?
Some Jira clone forms provide an option to include subtasks. If you see that option, use it when the same breakdown applies to the new work. Then inspect the resulting issue and subtasks, since owners, status, and other details may need to change. If no option appears, create the required subtasks separately.
Conclusion
Cloning a Jira issue can save time when you need a proven structure for similar work. Open the original, use the clone action, review the available fields, and check the new issue before your team starts.
That final review helps prevent stale details, unclear ownership, and missing task relationships from slowing everyone down. Treat each clone as a new piece of work that deserves a quick check, and your team can reuse useful context with fewer surprises.