How to Clone a Jira Ticket: A Step-by-Step Guide with Examples
Need a similar issue fast? Learn how to clone a Jira ticket step by step and avoid missing key details. Read now to get started.
Need a second Jira issue for a similar task, bug, or recurring request? Rebuilding it by hand can waste time and leave important details behind. Worse, a missed priority, attachment, or link can send the next person in the wrong direction.
To clone a Jira ticket, open the issue, select More, then choose Clone. Review the fields in the clone form, adjust the new issue’s summary and destination if needed, and create it. Jira’s options vary by version and configuration, so check the result before assigning work. But here’s the truth: cloning saves effort only when you verify what carried over. This guide walks you through the steps, explains what to check, and shares practical examples to help you create a useful copy without creating confusion.
How to Clone a Jira Ticket
Use these steps to create a separate Jira issue with details copied from an existing one. The exact dialog can differ between Jira editions and project configurations.
Open the issue you want to copy. Confirm that it is the right ticket by checking its summary, project, and issue key. For example, you might start with SHOP-214, “Add password reset email.”
Open the actions menu. Select More near the issue’s main actions, then choose Clone. If you cannot see that option, your project permissions or Jira configuration may restrict it.
Review the clone form. Jira may let you edit the summary, project, issue type, or other fields. It may also offer options for linked issues or subtasks. Check each available option instead of assuming every field will carry over.
Give the new issue a clear purpose. Replace a generic “Clone of” prefix with a summary that explains the new work. For example, change “Clone of Add password reset email” to “Add password reset email for French accounts.”
Create the clone. Submit the form and wait for Jira to create the new issue. The original issue remains separate, so updates to one ticket generally do not update the other.
Verify the result. Open the new issue and check its project, description, assignee, priority, attachments, links, and any required custom fields. Update anything that does not fit the new task.
Here’s why the final check matters: Jira’s clone behavior can depend on your setup. A ticket may look complete while still carrying an old assignee, sprint, or due date.

What Jira Usually Copies—and What to Check
A clone commonly carries over issue details such as the summary, description, and selected field values. Which fields appear in the clone depends on the Jira version, project configuration, and permissions.
Comments, work logs, change history, and attachments may be handled differently from ordinary issue fields. Treat them as items to verify, especially when the new ticket needs a complete record or access to the same supporting materials.
Cloning can also create a relationship between the original and new issues. Jira may label that relationship as a clone link, helping teammates understand why two tickets look similar. Check the issue links after creation if traceability matters.
For example, when copying a bug report for a second browser, keep the reproduction steps but update the browser, version, and expected behavior. A quick review helps the new issue stand on its own.
Examples of When Cloning Helps
Cloning works well when a new issue needs much of the same structure as an existing one. It saves setup time while giving the new task its own status, assignee, and discussion.
Recurring maintenance: Clone a monthly certificate check, then update its due date and owner. The new ticket can retain the checklist while tracking this month’s work separately.
Related bugs: Clone a login issue reported on one browser, then revise the reproduction details for another browser. Keep only the steps that still apply.
Regional launches: Clone a release task for another market, then change the locale, legal requirements, and target date. This keeps the basic workflow familiar without treating the work as identical.
The best part? You can reuse a proven structure without asking the team to treat each instance as one ongoing ticket. That makes progress and ownership easier to follow.
Cloning, Creating, or Moving an Issue
Choose the action that matches what you need to track. Cloning creates a separate issue that starts with selected details from an existing ticket. Creating a fresh issue gives you a blank slate.
Moving an issue changes where the existing ticket lives, such as changing its project or issue type. It does not create a second copy for a separate piece of work. Let me explain with a simple example: if the same bug needs independent fixes in two products, cloning may fit. If the bug belongs in a different project, moving it may be the better choice.
| Action | What happens | Useful when |
| Clone | A new issue is created with selected details from an existing issue. | You need separate tracking for similar work. |
| Create | A new issue starts with the fields and structure you provide. | The new work has little in common with an existing ticket. |
| Move | An existing issue is transferred to another project or issue type. | The current ticket should continue under a different project or type. |
Before choosing, consider whether the work needs independent ownership, status, and history. If it does, a clone or a new issue may be more suitable than moving the original.
How to Keep Cloned Tickets Useful
A clone is a starting point, not a finished task. Remove details that belong only to the original issue, then make the new ticket specific enough for someone else to act on.
Rewrite the summary. Make the new task recognizable in a backlog. “Clone of login bug” tells the team little; “Fix login timeout on Safari 17” gives them a clear direction.
Update ownership and timing. Review the assignee, reporter, sprint, due date, and priority. Old values can create false expectations.
Review links and subtasks. Keep related items that still apply, and remove or revise relationships that could mislead the team. Confirm whether subtasks were copied if they are needed.
Check access and sensitive details. A copied description or attachment may include information that is unsuitable for the new project. Confirm the intended audience can access the new issue.
You might be wondering: should you clone a ticket every time work repeats? Only when separate tracking is useful. For a tiny recurring action, a checklist or automation may be simpler than creating another issue.
Project and Knowledge Management with ONES.com
ONES.com combines project management and knowledge management in one platform. ONES Project supports project work, while ONES Wiki provides a knowledge base; the products are sold separately.

For teams comparing Jira alternatives, ONES Project includes Jira-compatible workflows, sprint management, automation, built-in reporting, and customizable workflows and fields. Its on-premise and other self-hosted deployments provide feature parity with the cloud version.
Core Capabilities
Pain: Teams repeat issue setup across similar projects. ONES capability: Jira-compatible workflows and customizable fields support consistent issue structures. Result: Teams can reuse a familiar process while adapting tickets to different projects.
Pain: Teams need visibility into project progress. ONES capability: Built-in reporting brings project status into view. Result: Project leads can review progress without relying on extra reporting plugins.
Pain: Sprint work is difficult to coordinate. ONES capability: ONES Project includes sprint management. Result: Teams can plan and track sprint tasks within their project workflow.
Pain: Repetitive steps consume time. ONES capability: Automation can handle configured workflow actions. Result: Teams can reduce manual follow-up for routine transitions and updates.
Pain: A team relies on multiple plugins for core project needs. ONES capability: Workflows, fields, reporting, and sprint management are available in the platform. Result: Teams may be able to reduce plugin dependence for those capabilities.
Pain: Teams need control over where their environment runs. ONES capability: ONES.com offers Cloud, On-Premise, Private Cloud, and Air-gapped deployments. Result: Teams can choose an environment that fits their infrastructure and security requirements.
Pain: Project work and team knowledge become disconnected. ONES capability: ONES Wiki offers knowledge management alongside ONES Project in the ONES.com platform. Result: Teams can manage project work and reference material within the same platform environment.
Pain: A team wants to evaluate a project management platform before a wider rollout. ONES capability: The free plan supports up to 30 seats. Result: A small team can try the product before deciding on a broader adoption.
Application Scenarios
Product teams managing recurring releases: A team can use ONES Project workflows and sprint management to coordinate repeated release tasks. Custom fields can distinguish the market, release date, or product area.
Organizations with restricted infrastructure: A team that cannot use a public cloud environment can evaluate On-Premise, Private Cloud, or Air-gapped deployment. Feature parity between cloud and self-hosted versions helps teams assess deployment needs without choosing a reduced feature set.
Teams linking project work with internal guidance: A product team can track an implementation in ONES Project and maintain related procedures in ONES Wiki. The products are sold separately, so teams can select the capabilities they need.
Common Challenges When Cloning Jira Issues
The Clone action is missing. Your permissions, project settings, or Jira configuration may limit access. Ask a Jira administrator to check the relevant permissions and project setup.
The new ticket contains stale details. An old assignee, deadline, or sprint can confuse the team. Review these fields immediately and replace values that do not apply.
Expected content did not carry over. Jira may treat comments, attachments, or subtasks differently from standard fields. Inspect the new issue and add or recreate any needed items.
Two issues appear to track the same work. This can happen when a clone is created without a distinct purpose. Clarify the difference in each summary and description, or close the unnecessary issue using your team’s process.
Frequently Asked Questions
Does cloning a Jira ticket change the original?
Cloning creates a separate issue, so changes to the new ticket generally do not change the original. The two issues may be linked to show their relationship. Review the clone after creation, since field behavior and link options can vary by Jira version and project configuration.
Will Jira copy comments and attachments to the new issue?
Do not assume that every comment, attachment, or activity detail will be copied. Jira’s clone behavior can vary, and these items may be handled differently from fields such as the summary or description. Open the new issue and verify anything the next assignee needs. Add missing material only when you have permission to share it.
Can I clone a Jira issue into another project?
That depends on the clone form, your permissions, and your Jira setup. If the form lets you select a destination project, choose it and review the available fields before creating the issue. Check that the destination uses compatible issue types and required fields. If Jira does not offer the destination, ask an administrator about project permissions or use the team’s approved process.
Are subtasks copied when I clone an issue?
Subtask copying depends on the options available in your Jira setup. Some clone forms may provide a setting for subtasks, while others may require you to create them separately. After cloning a parent issue, check its child issues and recreate any that are needed. Update their summaries, owners, and due dates to fit the new work.
What is the difference between cloning and moving a Jira issue?
Cloning creates a separate issue with selected details from the existing ticket. Moving changes the location or type of the existing issue. Clone when the work needs independent tracking, such as a similar bug in another product. Move when the original ticket should continue under a different project or issue type.
Conclusion
To clone a Jira ticket, open the issue, select More, choose Clone, and review the new issue before assigning work. Update the summary, ownership, dates, links, and any details that belong only to the original.
A careless clone can create confusion; a checked clone can save setup time and preserve useful context. Use cloning when similar work needs separate tracking, and choose a fresh issue or a move when that better fits the task. A short review after creation helps keep the team’s backlog clear and actionable.