How to Clone a Jira Issue: Step-by-Step Guide for Teams
Need to know how to jira clone an issue without stale details? Follow this guide to copy and customize issues for your team. Read now.
To clone a Jira issue, open it, choose More or the issue actions menu, select Clone, adjust the copied details, and create the new issue. The clone gives your team a starting point for repeatable work, such as a recurring release task or a similar customer request.
But here's the truth: a quick copy can also carry over details that no longer apply. The wrong project, stale dates, or an unchanged summary can confuse teammates and lead to work being missed. Jira’s menus and available clone options can vary by version, project settings, and permissions, so the steps may not look identical for everyone.
Here's how to clone an issue carefully, check what came across, and avoid common cleanup problems. You’ll also see when cloning makes sense, when another action is better, and how teams can manage repeatable work more consistently.
How to clone a Jira issue: step-by-step
Use these steps to create a separate issue with selected details copied from an existing one. The exact labels and options can differ between Jira Cloud and self-managed installations.
Open the issue you want to copy. Check its project, summary, description, and current status. Confirm that it is a useful model for the new task, rather than an outdated or unusual example.
Open the issue actions menu. Look for More, an ellipsis, or another actions control near the issue details. Menu placement can change with the Jira layout and project configuration.
Select Clone. If you cannot see this action, your permissions or Jira configuration may not allow it. Ask a project administrator to check access or available issue actions.
Review the clone form. Jira may let you change the summary and choose which details to carry over. Some clone forms also show options for related items, depending on your setup.
Make the new issue distinct. Replace dates, names, acceptance criteria, and other details that belong only to the earlier task. For example, change “Prepare April release notes” to “Prepare May release notes.”
Create the clone. Submit the form, then open the new issue. Check its issue key, project, summary, and any fields your team relies on.
Confirm links and ownership. Review any copied relationships or assigned people. Add the right parent, sprint, labels, or assignee if your team needs them.
The new issue should have its own issue key and be managed separately. Treat the clone as a draft until you’ve checked its details and confirmed that it belongs in the intended project.

What Jira cloning does—and what it may leave out
Cloning creates a separate issue using selected details from an existing one. It is useful when several tasks share a reliable structure, but the copy should not be assumed to match every field or relationship.
For example, a support team might clone a standard investigation task for a new customer incident. The summary and description can provide a helpful starting point, while the customer name, urgency, and reproduction steps need fresh review.
Here's why a final check matters: Jira administrators can configure fields and workflows differently. The clone action may offer different choices across projects, and some related details may need to be added or checked separately.
Cloning also does not mean the new issue automatically belongs in the same sprint or has the right owner. Check these settings before teammates begin work.
When to clone an issue—and when to choose another action
Clone an issue when the new work is separate but benefits from a similar starting structure. Common examples include recurring maintenance tasks, standard testing activities, and follow-up investigations with a familiar checklist.
Suppose your team runs a release review each month. A clone can preserve useful review steps, while you update the release name, dates, reviewers, and links for the new cycle.
Use a different action if you need to keep working on the same task. Editing the existing issue preserves its identity and history. If the issue simply belongs in another project, ask your Jira administrator whether moving it is appropriate.
You might be wondering: should you clone a parent issue with subtasks? Check the clone form carefully. If related tasks are offered as options, decide whether each one applies to the new work before creating the copy.
What to review before and after creating a clone
A short review prevents a copy from carrying forward outdated instructions or ownership. Before cloning, confirm that the issue is current, clearly written, and suitable as a template for the next task.
Summary: Replace old dates, release names, customer names, or project references.
Description: Remove instructions that apply only to the earlier task, then add details for the new work.
People and timing: Check assignees, due dates, priority, and sprint placement.
Relationships: Review parent, epic, and other issue links where relevant.
Project and status: Confirm the new issue is in the intended project and follows the correct workflow.
The best part? This check can take less time than resolving a duplicate task later. For example, updating a stale assignee before work starts avoids sending notifications to the wrong teammate.
Ways to make issue cloning more consistent across a team
Agree on which issue types are suitable for cloning. A recurring QA task may be a good candidate, while a one-off incident with sensitive or unusual details may not be.
Keep reusable examples clear and current. If your team repeatedly clones an issue with outdated steps, every new copy will require extra cleanup. Assign someone to review common templates when your process changes.
Use a simple naming convention to distinguish new work. Adding the current release, account, or cycle to the summary can help teammates recognize the clone quickly.
Let me explain: cloning saves effort only when the copied structure is still useful. A two-minute review can preserve the benefit without turning old assumptions into new tasks.
Issue workflow management with ONES.com
ONES.com is a unified platform for project management and knowledge management, powered by ONES Assistant. Teams evaluating a broader workflow may consider ONES Project as a Jira alternative, while ONES Wiki is a Confluence alternative; the products are sold separately.

For teams whose challenge extends beyond creating one clone, the practical question is how to keep recurring tasks, reporting, and team knowledge consistent. ONES.com offers cloud and self-hosted deployments, including On-Premise, Private Cloud, and air-gapped options. Its self-hosted version has feature parity with cloud, and its free plan supports up to 30 seats.
Core capabilities
Issue workflows feel inconsistent → ONES Project supports custom workflows → teams can shape task movement around their review and approval stages.
Important task details vary between projects → Custom fields help teams capture project-specific information → recurring work can be organized around the details teams need.
Teams need visibility into progress → Built-in reporting provides project views → leads can review work without relying on separate reporting add-ons.
Repeatable delivery work needs coordination → Sprint management supports planning → teams can organize work into cycles and monitor progress.
Manual handoffs create repeated steps → Automation supports workflow actions → teams can reduce routine administration where configured.
Teams want a familiar transition from Jira → Jira-compatible workflows support familiar ways of organizing work → teams can evaluate an alternative without discarding every established practice.
Too many add-ons complicate administration → Core workflow, reporting, and planning capabilities are built in → teams may be able to reduce their reliance on plugins.
Hosting requirements restrict platform choices → Cloud, On-Premise, Private Cloud, and air-gapped deployments are available → teams can assess a deployment that fits their environment.
Application scenarios
A team standardizing recurring work: A delivery team can define common workflows and fields for repeatable tasks. Members still review each new issue to update dates, ownership, and project-specific details.
A team reviewing a Jira alternative: A team can assess ONES Project’s Jira-compatible workflows, reporting, sprint management, and automation against its current needs. It should verify migration and day-to-day behavior during its evaluation rather than assume every setup works identically.
A team with restricted hosting needs: An organization can compare cloud and self-hosted deployment options, including air-gapped environments. It can also evaluate whether ONES Project and ONES Wiki should be used together or purchased separately.
Common challenges when cloning Jira issues
The Clone action is missing. Your role, project permissions, or configuration may limit available actions. Ask a project administrator to confirm your access and the project’s settings.
The new issue contains outdated details. Review the summary, description, dates, and people before work begins. Update information that belongs only to the earlier task.
The clone appears in the wrong place. Confirm the project shown in the clone form and check the new issue after creation. If it belongs elsewhere, ask an administrator about the correct project process.
Related work is missing or unexpected. Inspect any clone options for subtasks or links, then review the new issue’s relationships. Add or remove relationships as your team’s workflow requires.
Several similar copies confuse the team. Use clear summaries and agree on when cloning is appropriate. Close or update accidental duplicates according to your team’s issue-handling process.
FAQs about cloning Jira issues
Does cloning a Jira issue change the original?
Cloning creates a separate issue, so you can update the new task without changing the original. The original remains useful for reference, while the clone receives its own issue key and can be assigned and managed independently. Still, review the clone before work starts. Copied details may not fit the new task, and available clone options vary with Jira configuration.
Can I clone an issue into a different project?
That depends on the clone options available in your Jira setup. Check the project field in the clone form before creating the issue. If the destination project is unavailable, your permissions or configuration may limit the action. Ask a Jira administrator about the appropriate process, which could involve another supported action rather than cloning directly.
Why can’t I see the Clone option?
The issue actions menu can vary by Jira version, project setup, and permissions. First, check the available actions menu on the issue. If Clone is not listed, ask a project administrator to confirm whether your role can create issues and whether the action is available for that project. The menu may also look different from instructions written for another Jira layout.
Does Jira copy subtasks when I clone an issue?
Clone behavior for subtasks can depend on the options presented in your Jira setup. If the clone form offers a setting for related tasks, review it before proceeding. After creation, open the new issue and check whether the subtasks are present and appropriate. Update their summaries, owners, and other details where needed.
Is cloning the same as moving a Jira issue?
No. Cloning creates a separate issue, while moving is used when an existing issue needs to change location or project, subject to your Jira setup. Choose cloning when the new work should have its own identity. Choose a move-related process when the same task should continue elsewhere, and check with your administrator if you are unsure.
Conclusion
Cloning a Jira issue is straightforward: open the issue actions menu, select Clone, review the available options, create the new issue, and verify its details. The important work is making sure the copy fits the new task before your team acts on it.
When cloning is hard to manage, stale details and duplicate work can create unnecessary confusion. A consistent review habit helps your team reuse useful task structure while correcting what has changed. For broader workflow needs, you can also evaluate ONES.com and its project management options against your team’s requirements.