How to Clone a Jira Ticket: Step-by-Step Guide for Teams
Need to duplicate an issue without missing key details? Learn how to clone a Jira ticket step by step and what to review. Read now.
Have you ever needed to repeat a Jira task and started recreating every field by hand? That takes time, and small omissions can leave the new issue missing a deadline, detail, or useful relationship.
It gets trickier when your team needs several similar tickets. A copied task can carry over details that no longer apply, while a manually recreated one can drift from the original in ways nobody notices.
But here's the truth: Jira’s built-in Clone action can create a new issue quickly, as long as you review what carries over. I’ll walk you through the steps, explain what to check, and share ways to keep cloned work clear and useful.
How to Clone a Jira Ticket: Step-by-Step
Open the issue you want to copy, choose More > Clone, review the clone options, and create the new issue. Then check its fields and relationships before your team starts work.
- Open the Jira issue. Go to the ticket you want to copy and confirm it contains the details you actually want to reuse. If the description or acceptance criteria are outdated, clean them up first.
- Choose the Clone action. On the issue view, open the More menu and select Clone. The menu location and available options can vary with your Jira version and configuration.
- Review the clone form. Jira may show a dialog with a suggested summary and optional settings. Adjust the summary so the new issue describes its own work, and inspect any options for copying attachments or subtasks.
- Make the new ticket easy to identify. Keep useful context, but replace wording that refers only to the original task. For example, change “Update checkout error text” to “Update mobile checkout error text” when the new ticket concerns a different product area.
- Create the cloned issue. Submit the form and note the new issue key. Jira usually creates the clone in the same project, though available behavior can depend on your setup.
- Verify before assigning work. Open the new ticket and check the project, issue type, summary, description, priority, dates, assignee, attachments, subtasks, and links. Correct anything that should differ before the ticket enters active work.
Here’s why that last check matters: cloning saves you from rebuilding a ticket, but it doesn’t decide whether every copied detail still makes sense. Treat the result as a draft until you have reviewed it.

What Jira Cloning Copies—and What to Review
A clone gives you a new Jira issue with some details carried over from the original. The exact fields and options can vary by Jira edition, project configuration, and enabled features, so don’t assume every value will transfer.
For example, a cloned bug report may retain its description and priority, while its assignee, due date, or custom fields need review. A copied attachment may also be irrelevant to the new task, even when it is useful for the original.
Think of a clone as a starting point, not a perfect twin. Keep reusable details such as setup instructions, then update context-specific information like the affected version, customer, deadline, or team.
Fields Worth Checking
- Summary and description: Remove references that only make sense for the original issue.
- Assignee and reporter: Confirm the right people own and raised the new work.
- Dates and priority: Reassess urgency and timing rather than inheriting them automatically.
- Custom fields and components: Check that the new issue points to the right team, product area, or release.
- Attachments, subtasks, and links: Keep only the items that help someone complete this ticket.
When to Clone a Ticket—and When to Start Fresh
Cloning is useful when two tasks share a repeatable structure. A release checklist, recurring maintenance task, or similar bug report can give you a reliable starting point without requiring a blank issue.
For example, your team might clone a standard quality check for each release. The steps stay consistent, while the version number, owner, and target date change. That pattern saves setup time and helps each release follow the same process.
Start fresh when the original issue is only loosely related or contains many details that no longer apply. If you need to remove most of the copied content, creating a new issue may be clearer than editing a clone.
You might be wondering: should you clone one ticket or create several at once? For a handful of related tasks, cloning can be practical. For a repeated process across many projects, consider a Jira template or automation option if your team has configured one.
Keep Cloned Tickets Clear for the Team
A cloned ticket can confuse teammates when its relationship to the original is unclear. Give the new issue a specific summary, explain what is different, and add context about why the work exists.
Suppose you clone a task for a second region. Mention the region in the title, update the affected market in the description, and set the correct owner. A teammate should be able to understand the new task without comparing every field with the original.
Where Jira displays a clone relationship or issue link, check that it helps explain the connection. A useful relationship shows why the tickets are related; it should not imply that one task is a duplicate if each requires separate work.
A Quick Review Before Work Starts
- Does the summary describe the new work?
- Are the owner, priority, and due date still correct?
- Do the description and acceptance criteria fit this ticket?
- Are copied attachments, subtasks, and links relevant?
- Can a teammate tell how this issue differs from the original?
Cloning Behavior, Permissions, and Common Variations
Jira’s screens and clone options can differ between Cloud and self-managed environments. Administrators can also change project settings and available actions, so your screen may not match another team’s instructions exactly.
If you cannot see Clone, check whether you have permission to create issues in the project and whether the action is available in your configuration. A project administrator can help confirm which permission or setting is involved.
Cloning across projects may require a different process from cloning within one project. If the new ticket belongs elsewhere, check whether your Jira setup offers the needed project choice or whether you should create an issue in the destination project and copy only the relevant details.
Let me explain: a few minutes of checking can prevent a ticket from landing in the wrong workflow or team queue. When the clone form does not offer the right controls, ask an administrator about the approved process instead of assuming Jira copied everything you need.
A Project Management Alternative: ONES.com
ONES.com is a unified platform for project management and knowledge management, powered by ONES Assistant. ONES Project handles project management and is positioned as a Jira alternative; ONES Wiki provides knowledge management as a Confluence alternative. They are sold separately.

If your team is evaluating how it manages work, compare the workflows and administration needs that sit behind repeated ticket creation. ONES Project supports Jira-compatible workflows, sprint management, custom workflows and fields, automation, and built-in reporting. These capabilities can help teams organize repeatable work within a project system instead of relying on manual ticket setup alone.
Where ONES Project Can Help
- Repeated ticket setup takes time: Jira-compatible workflows help teams preserve familiar ways of organizing work, reducing the need to rebuild processes during a transition.
- Project fields do not fit team needs: Custom fields let teams capture relevant task details, so work can be organized around the information they actually track.
- Work moves through changing stages: Custom workflows allow teams to shape issue states and transitions, giving each project a process that fits its work.
- Sprint planning needs structure: Sprint management supports teams that plan and track work in iterations.
- Repeated actions require manual effort: Automation can handle configured actions, helping teams reduce routine administration.
- Progress is hard to assess: Built-in reporting gives teams project views for monitoring work without depending on additional plugins for every reporting need.
- Teams want fewer add-ons: Native capabilities can reduce plugin reliance for supported project management needs, which can simplify administration.
- Hosting requirements vary: ONES.com offers Cloud, On-Premise, Private Cloud, and Air-gapped deployments, giving teams deployment choices that fit their environment.
For instance, a software team could use ONES Project to manage sprint work with custom fields for affected product areas and built-in reports for progress reviews. A team that needs a restricted network can evaluate an air-gapped deployment as part of its infrastructure planning.
ONES.com offers a free plan for up to 30 seats. Its cloud and self-hosted versions have full feature parity, so teams can compare deployment needs without assuming that self-hosting means giving up product features.
The right choice depends on your workflow, deployment requirements, and the features your team needs. If your immediate need is simply to clone a Jira issue, use Jira’s Clone action and review the new ticket. If you are assessing project management more broadly, ONES Project is one option to evaluate.
Common Challenges When Cloning Jira Issues
The Clone Action Is Missing
Problem: You open the issue menu but cannot find Clone. Solution: Ask a project administrator to check your issue creation permissions and whether cloning is enabled or available in your Jira configuration.
The New Ticket Has Irrelevant Details
Problem: The clone retains a date, owner, or description that only applied to the original task. Solution: Review key fields immediately after creation and update details before assigning the ticket or including it in a sprint.
Several Clones Look Identical
Problem: Teammates cannot tell which ticket covers which region, product, or release. Solution: Make each summary specific and add a short explanation of the difference in the description.
Attachments or Subtasks Add Clutter
Problem: Copied items make the new issue harder to follow or point to work that does not belong. Solution: Check every copied attachment and subtask, then remove or update anything that does not support the new task.
FAQs About Cloning Jira Tickets
Does cloning a Jira ticket change the original?
No. Cloning creates a separate issue, so changes you make to the new ticket do not normally update the original. You can edit the clone’s summary, description, and other fields without changing the original issue. Still, check how your Jira project handles links and shared items, because a relationship between issues may remain visible after cloning.
Can I clone a Jira issue into another project?
Cloning behavior depends on your Jira version and project configuration. The usual Clone action creates an issue in the same project, and cross-project options may not be available in every setup. If the new work belongs in a different project, check the clone form or ask an administrator about the approved process. You may need to create an issue in the destination project and copy the relevant details.
Why can’t I see the Clone option in Jira?
The option may be unavailable because of your permissions, project settings, or the Jira configuration your team uses. Confirm that you can create issues in that project, then ask a project administrator to check whether cloning is available. If your team uses a customized issue view, the action may also appear in a different menu.
Will Jira copy assignees, attachments, and subtasks?
Do not assume every field or related item will carry over. Jira’s behavior can vary with the edition, configuration, and choices shown in the clone dialog. Review the new issue after creating it, especially its assignee, attachments, subtasks, dates, and custom fields. Remove anything that does not belong to the new task and confirm that required details are present.
Is cloning the same as duplicating an issue?
People often use “clone” and “duplicate” to describe creating a similar issue, but Jira’s Clone action creates a separate issue with its own key. The new ticket can still be linked to the original, depending on how Jira handles the clone relationship in your setup. If both tickets represent separate work, explain that distinction in their summaries or descriptions.
Conclusion
To clone a Jira ticket, open the issue, choose More > Clone, review the available options, and create the new issue. Then verify its summary, ownership, dates, fields, attachments, subtasks, and links before work begins.
Cloning can save time when tasks share a useful structure, but a quick review helps prevent stale details and confusing duplicates. If Jira’s Clone action is unavailable, check permissions and project configuration with an administrator.
When repeated ticket setup points to a broader project workflow need, compare the process your team wants with available project management options. A careful clone—or a better-fitting workflow—can help your team keep work clear and actionable.