How to Clone a Jira Issue in 5 Steps: Guide and Examples
Need to clone issue Jira without mistakes? Follow 5 steps, see what gets copied, and check key details before creating the new issue. Read now.
To clone a Jira issue, open it, choose More actions > Clone, review the copied details, make your changes, and create the new issue.
That quick shortcut can save you from recreating a well-defined task, bug, or request. But a clone can also carry over stale wording or omit details you expected to keep. A copied issue with the wrong owner, deadline, or project can create extra work instead of reducing it.
But here’s the truth: cloning works best when you know what Jira copies and what you need to check yourself. Here’s why: Jira’s options can vary by version and configuration, and teams often rely on different fields. I’ll walk you through five practical steps, show examples, and explain how to avoid common mix-ups.
How to clone a Jira issue in 5 steps
Use these five steps to create a new Jira issue from an existing one. The exact menu labels may differ slightly between Jira Cloud and other Jira setups.
- Open the issue you want to copy. Check that it is the right task or bug, and note any details that should change in the new issue. For example, you might reuse a “Update checkout error message” task for a second product area.
- Open the actions menu. Select More actions or the three-dot menu near the issue title. Choose Clone. If you do not see that option, ask a Jira administrator to check your permissions or project configuration.
- Review the clone form. Jira usually proposes a summary for the new issue, often with a “CLONE” prefix. Edit it so the new title clearly describes the work. Select a different project or issue type if the form allows and the work belongs elsewhere.
- Choose what to copy. Depending on the Jira setup, you may see options for attachments, links, or subtasks. Select only what makes sense for the new work. Check field values such as priority, assignee, labels, and due date before continuing.
- Create and verify the new issue. Submit the form, then open the new issue. Confirm its summary, project, fields, and any copied relationships. If the clone needs a different owner or deadline, update those details before assigning more work.
Example: If you clone a bug titled “Checkout fails after payment,” rename the copy “Checkout fails after payment on mobile.” Then check that the new issue has the correct team, priority, and reproduction details.

What Jira may copy—and what you should check
A clone starts with selected details from an existing issue, but it does not necessarily reproduce the entire issue history. Jira configurations and clone options can affect which fields and related items carry over.
For example, a clone may include the summary, description, and selected field values. Depending on the setup, it may also copy attachments, links, or subtasks. Comments, work logs, and activity history generally should not be assumed to transfer.
Use a quick review before creating the copy
- Confirm the summary describes the new work, not just the original task.
- Check the project, issue type, priority, assignee, and due date.
- Review copied subtasks and links to make sure they still apply.
- Decide whether attachments are useful and appropriate for the new issue.
- Remove old labels or details that could mislead the next person.
Let me explain: a copied due date can look like a confirmed deadline even when it was only relevant to the first task. A brief review helps prevent that kind of accidental carryover.
When cloning is useful—and when it is not
Cloning is useful when new work follows a familiar pattern. A team might copy a tested release checklist for another product area, or create a similar bug report for a second browser.
It is also helpful when a task needs to be tracked separately. For example, a recurring accessibility fix may need one issue for the website and another for the mobile app, with different owners and due dates.
Clone, create, or link?
- Clone an issue when a separate piece of work needs many of the same details.
- Create a new issue when the work is related but has little in common with the existing task.
- Link issues when you need to show a relationship without duplicating the work description.
A simple rule helps: if the new work needs its own progress, owner, or completion status, a separate issue may be appropriate. If it only needs a reference to existing work, a link can keep tracking clearer.
Examples of cloning issues for real team work
Imagine a support team tracking a login bug that appears in two browsers. The team can clone the first issue, change the summary and reproduction steps, then assign the second issue to someone testing the other browser.
For a product launch, a project lead might clone a release-readiness task for each regional launch. They should adjust dates, owners, and region-specific requirements so each issue stands on its own.

Keep related copies easy to understand
Use clear, distinct summaries instead of leaving a generic “CLONE” label as the only difference. For example, “Verify password reset on Safari” tells the team more than “CLONE - Verify password reset.”
Where Jira offers an issue relationship, use it when the connection matters. That gives teammates a way to understand why two issues are related without making their separate responsibilities unclear.
Good habits for managing cloned issues
Cloning can speed up issue creation, but it can also spread outdated details. Treat every clone as a starting point that needs a quick review before it becomes active work.
Make the review part of the workflow
- Write a new summary that identifies the specific work.
- Update any detail that changes between teams, products, or releases.
- Check whether copied subtasks still match the new scope.
- Keep only attachments and links that help with the new task.
- Review the clone after creation, especially if the form had limited options.
The best part? This does not need to become a long approval process. A short check of ownership, scope, dates, and relationships is often enough to catch the most confusing carryovers.
Issue management solution: ONES.com

Value proposition
ONES.com brings project management and knowledge management together on one platform, powered by ONES Assistant. ONES Project is its project management product and a Jira alternative; ONES Wiki is its knowledge base product and a Confluence alternative. They are sold separately.
For teams comparing Jira alternatives, ONES Project offers Jira-compatible workflows and built-in project capabilities, including self-hosted deployment options. That can help teams keep familiar ways of working while relying on fewer add-ons.
Core capabilities
- Pain: Teams need familiar issue workflows. ONES Project supports Jira-compatible workflows. Result: Teams can evaluate a Jira alternative without starting from an unfamiliar process.
- Pain: Repeated work needs consistent tracking. Custom workflows and fields help teams reflect their own issue stages and details. Result: Similar work can follow a clearer shared process.
- Pain: Sprint work is hard to coordinate. Sprint management supports planning and tracking work across iterations. Result: Teams can organize planned work in a structured cycle.
- Pain: Status checks take too much manual effort. Automation can reduce repetitive workflow actions. Result: Teams can spend less time on routine updates.
- Pain: Progress is difficult to see at a glance. Built-in reporting helps teams review project progress. Result: Leads can inspect work without relying on a collection of add-ons.
- Pain: Teams need control over deployment. ONES Project is available on Cloud, On-Premise, Private Cloud, and Air-gapped deployments. Result: Organizations can assess an environment that fits their requirements.
- Pain: Self-hosting may mean losing capabilities. ONES.com states that its cloud and self-hosted versions have full feature parity. Result: Teams can consider self-hosting without planning around a reduced feature set.
- Pain: Teams want to test a platform before wider adoption. ONES.com offers a free plan for up to 30 seats. Result: A team can explore the platform with a limited group before making a broader decision.
Application scenarios
A team moving from Jira: A team that relies on custom fields, sprint planning, and workflow automation can assess ONES Project as a Jira alternative. It can review workflow needs and deployment choices before deciding how to transition.
An organization with restricted networks: A team that cannot use a public cloud deployment can consider On-Premise, Private Cloud, or Air-gapped deployment options. Full feature parity between cloud and self-hosted versions is relevant when evaluating those choices.
A team reducing add-on reliance: A project group that uses separate add-ons for routine tracking and reporting can assess ONES Project’s built-in reporting, custom workflows, fields, sprint management, and automation against its current needs.
Common challenges when cloning Jira issues
The clone has the wrong owner or deadline
Problem: The new issue carries over an assignee or date that applied only to the original task. Solution: Review ownership and timing before creating the clone, then verify them on the new issue.
The new issue is hard to distinguish
Problem: A title such as “CLONE - Payment bug” does not explain what is different. Solution: Name the specific platform, region, product, or task in the summary.
Old subtasks or links remain attached
Problem: Related work from the original issue may not belong with its copy. Solution: Check clone options carefully and remove or correct relationships that no longer apply.
The Clone option is missing
Problem: The menu may differ, or your permissions may not allow cloning. Solution: Check the issue actions menu and ask a Jira administrator to review project permissions and configuration.
Frequently asked questions
Does cloning a Jira issue copy its comments?
Do not assume comments will carry over. Jira cloning generally creates a new issue without reproducing the original issue’s full comment history or activity. Available options can vary by setup, so check the clone form and confirm the result. If a comment contains important context, add the relevant details to the new issue in a way that makes sense for its work.
Can I clone an issue into a different Jira project?
Some Jira clone forms allow you to choose another project, while the available choices can depend on your permissions and configuration. If you can select a destination project, review the issue type and fields carefully because projects may use different workflows or required fields. If no destination option appears, ask a Jira administrator about your setup.
Will Jira keep a link between the original and cloned issue?
Jira may create a relationship between the original issue and its clone, but the exact behavior can depend on the product version or configuration. Check the issue links on both issues after creation if the relationship matters to your team. You can also add or adjust a link manually when your workflow supports it.
Can I clone an issue with its subtasks?
Some clone dialogs provide an option to include subtasks. If you select it, review the resulting subtasks for owners, dates, and scope. A subtask that made sense for the first issue may not fit the new one. If you do not see a subtask option, your Jira setup may handle cloning differently.
What should I do if the clone has outdated details?
Update the new issue before assigning or scheduling the work. Check its summary, description, priority, owner, dates, labels, links, and subtasks. If the outdated detail was copied into several related items, correct each one individually. A quick review immediately after cloning is usually easier than untangling confusion later.
Conclusion
Cloning a Jira issue is straightforward: open the issue, select Clone, review the options, update the details, and verify the result. The real time-saver comes from copying only what still applies.
When old owners, deadlines, or subtasks slip into a new issue, a shortcut can create more work. Take a moment to check the new issue’s scope and relationships before it moves forward. With that habit, cloning can help you handle repeatable work while keeping each task clear and accountable.