How to Clone a Jira Issue: Steps, Tips, and Examples in 2026
Need to clone an issue in Jira without missing key details? Follow these 2026 steps, tips, and examples, then review what carries over. Read now.
Copying a Jira issue by hand can mean recreating its fields, links, and subtasks one at a time. That takes longer than it should, and a missed detail can leave the new task incomplete.
But here's the truth: Jira has a built-in clone action, and you can use it to create a new issue without rebuilding everything from scratch. The result still needs a quick review, because cloning may not carry over every detail you expect.
Here’s how to clone an issue in Jira, what to check before you start, and how to avoid common mistakes. I’ll also cover when cloning makes sense, when a fresh issue is safer, and how teams can keep repeatable work organized.
How to clone a Jira issue
Open the issue you want to copy, choose the clone action, review the available options, and create the new issue. Jira’s interface and available fields can vary by version and configuration.
Open the issue. Navigate to the Jira issue you want to duplicate. Confirm that you have the right issue by checking its summary, project, and key.
Find the clone action. Open the issue’s More menu and select Clone. In some Jira versions, the action may appear in a different menu or under an issue actions menu.
Review the clone form. Jira usually suggests a summary that identifies the new issue as a clone. Edit it so the new task describes its own work clearly, such as changing “CLONE - Review payment flow” to “Review payment flow for mobile checkout.”
Choose what to carry over. Review the available fields and options. Depending on your Jira setup, you may be able to include attachments, links, or subtasks. Select only the details that apply to the new work.
Check the project and issue type. Cloning often creates an issue in the same project. If your Jira version or workflow offers a destination choice, verify the project and issue type before continuing.
Create the clone. Select the confirmation button, such as Create or Clone. Jira creates a new issue with its own issue key; the original remains unchanged.
Inspect the new issue. Check its summary, assignee, dates, links, attachments, subtasks, and workflow status. Update anything that should differ before assigning or starting the work.
Here’s why that final check matters: a clone can look complete while still carrying an old assignee, deadline, or project-specific value. A minute of review can prevent confusion later.

What Jira cloning copies—and what to verify
Cloning gives you a new issue that reuses selected details from an existing one. It does not turn the original into a second active task, and changes to the clone do not update the original.
Exactly what Jira copies depends on the version, configuration, and options shown in the clone form. Commonly carried-over details can include the summary, description, issue type, and some field values. Optional items may include attachments, links, or subtasks.
Do not assume that comments, work logs, history, status, or every custom field will transfer. For example, a cloned bug might retain its reproduction steps but need a new assignee and release target.
Before using the clone for active work, compare the new issue with the original. Keep reusable information, then replace details tied to the original request.
When cloning is better than creating a fresh issue
Clone an issue when the new task follows a familiar pattern and the original contains useful details. A recurring security review, for instance, might need the same checklist and issue type each quarter.
A fresh issue is usually safer when the new work has different requirements or ownership. If an old task contains customer-specific details, outdated acceptance criteria, or a closed sprint assignment, copying it may create more cleanup than starting over.
You might be wondering: should you clone a parent issue with subtasks? Do that only when the same breakdown still fits. If the new task needs different steps, create the parent and add relevant subtasks individually.
A simple rule helps: clone when the structure is reusable; start fresh when the context has changed. The choice can save time without carrying irrelevant details into the next task.
Tips for cleaner Jira clones
Give the new issue a specific summary rather than leaving a generic “CLONE” label. “Update onboarding emails for French launch” tells the team what changed and gives the issue a useful search result.
Check people and dates first. The original assignee may be on another team, and an old due date could make a new task appear overdue. Review project-specific fields, too, especially release, component, and sprint selections.
Let me explain: cloning is most useful when you treat it as a starting point, not a final review. For recurring work, agree on which fields should remain consistent and which must be updated each time.
If a task repeats often, consider documenting the steps or creating a team-approved issue template. That gives teammates a reliable pattern without relying on one old issue that may contain stale details.
Examples: cloning common Jira issues
Recurring quality assurance checks
Suppose your team tests checkout before each major release. Clone a previous test issue to reuse its test environment details and acceptance criteria, then update the release, dates, and assigned tester.
Review any linked defects or old attachments before work begins. A link to last quarter’s defect might confuse the team if it does not apply to the current release.
Similar customer requests
A support team may receive two requests to add the same account feature for different customers. Cloning can preserve the technical investigation steps, while the new summary, customer details, priority, and acceptance criteria are changed.
Be careful with private or customer-specific information. Remove details that do not belong in the new issue, and confirm that the new task has the correct project permissions.
Work with repeated subtasks
For a standard launch, a parent issue may have subtasks for testing, documentation, and deployment. If the next launch follows the same process, cloning those tasks can save setup time.
Check each child issue after cloning. Update owners and dependencies, and remove any subtask that does not apply to the new launch.
Issue-management solution: ONES.com

Value proposition
ONES.com brings project management and knowledge management together in a unified platform powered by ONES Assistant. ONES Project is the project management product and a Jira alternative; ONES Wiki provides knowledge management as a Confluence alternative. They are sold separately.
For teams handling repeated work, connected project workflows and knowledge practices can make it easier to maintain consistent task details. You can choose cloud or self-hosted deployment, including on-premise, private cloud, and air-gapped options.
Core capabilities
Disconnected task details: ONES Project supports Jira-compatible workflows, helping teams carry familiar ways of working into a Jira alternative.
Limited visibility into progress: Built-in reporting gives teams a way to review project status without relying on separate reporting add-ons.
Workflows that do not fit the team: Custom workflows let teams shape issue progression around their approval and delivery needs.
Fields that miss important context: Custom fields let teams capture details relevant to their projects, so repeatable tasks can be described more clearly.
Sprint planning needs: Sprint management supports teams organizing and tracking iterative development work.
Repetitive manual actions: Automation can handle selected workflow actions, reducing routine coordination work.
Project work separated from team guidance: ONES Wiki can hold knowledge alongside project work when teams choose both products.
Deployment requirements vary: Teams can choose Cloud, On-Premise, Private Cloud, or Air-gapped deployment, with full feature parity between cloud and self-hosted versions.
Evaluating fit before wider adoption: The free plan supports up to 30 seats, giving a team room to assess the platform with a small group.
Application scenarios
Repeated development work: A software team can use ONES Project to organize sprint tasks, customize fields for release details, and automate selected workflow steps. Teammates can then follow a consistent process for similar work.
Restricted environments: A team that cannot use a public cloud service can evaluate ONES Project’s On-Premise, Private Cloud, or Air-gapped deployment options. Its deployment choice can reflect its environment while retaining feature parity with the cloud version.
Project work with shared guidance: A team can use ONES Project for task coordination and ONES Wiki for internal knowledge when both products fit its needs. This can help keep working practices accessible alongside project activity.
Common challenges when cloning Jira issues
The clone has the wrong owner. Jira may carry over an assignee or another people-related field. Check the new issue’s owner and team before assigning work.
Old dates or sprint details remain. A cloned issue can retain values that belong to the original timeline. Update due dates, release details, and sprint selection before adding the task to current work.
Related work is missing. Links and subtasks may depend on the options available in your Jira setup. Compare the new issue with the original and add any necessary relationships manually.
Confidential details carry over. The description or attachments may include information that does not belong in the new task. Review access and content before sharing the clone with another team.
The team cannot find the new issue. A generic clone summary makes search harder. Write a clear summary and share the new issue key with the people who need it.
FAQs about cloning Jira issues
Does cloning a Jira issue change the original?
No. Jira creates a separate issue with its own key, and the original issue remains in place. Editing the clone does not normally change the original, either. Still, review links and related tasks after cloning, because those relationships can affect how people navigate between issues. If you are unsure what your setup carries over, test the clone action with a low-risk issue first.
Can I clone a Jira issue into a different project?
That depends on the Jira version and the options available in your configuration. Some clone actions create the new issue in the same project, while other workflows may allow a destination choice. If the clone form does not let you choose another project, create the issue in the destination project and copy the relevant details manually. Check required fields and issue types before submitting.
Will Jira clone comments, attachments, and subtasks?
It depends on the options presented by your Jira setup. Attachments, links, or subtasks may be available as clone choices, but you should not assume they are included. Comments and work history are also not details to count on transferring. After creating the clone, check the sections that matter for the task and copy or recreate any missing information you are allowed to share.
Can I clone an issue without using the “CLONE” prefix?
Often, yes. Jira may suggest a summary with a clone label, but you can usually edit the summary in the clone form. Replace it with a concise description of the new work before creating the issue. If your team uses a naming convention, follow it so the new task remains clear in search results, boards, and reports.
Conclusion
Cloning a Jira issue is a quick way to reuse useful task details: open the issue, select Clone, review the available options, and create a separate issue. Then check the new task’s fields, ownership, dates, links, and subtasks.
The main risk is carrying over details that belong only to the original. Treat the clone as a starting point, and update it before work begins. When the work is genuinely different, a fresh issue may be the cleaner choice.
That small review can prevent the bigger headache of incorrect assignments or stale requirements. With a clear process, you can reuse Jira issue structure while keeping each new task accurate and relevant.