How to Clone an Issue in Jira: A Step-by-Step Process Guide
Need to clone an issue in Jira without losing key details? Learn how to jira clone an issue safely with this step-by-step guide. Read now to get started.
Duplicating a Jira issue sounds simple until the new ticket loses an attachment, keeps the wrong sprint, or lands with a confusing summary. A rushed clone can also create duplicate work for teammates who cannot tell which issue is current.
Small differences between Jira versions add another wrinkle. The clone menu and available options may vary, and some details—such as comments or subtasks—may not carry over automatically.
But here's the truth: you can clone an issue safely with a short review before and after creation. I’ll walk you through the Jira steps, explain what to check, and show how to avoid common cleanup problems.
How to clone an issue in Jira
Open the issue, choose the clone action, review the fields and available options, then create and verify the new issue. You’ll need permission to view the original and create issues in the destination project.
-

Open the issue you want to duplicate
Go to the Jira issue and confirm that it is the correct one. Check its project, issue type, summary, and status before you start.
If several tickets look similar, compare their issue keys and descriptions. Cloning the wrong ticket can copy outdated requirements into a new task.
Choose the clone action
Open the issue’s action menu, often labeled More, and select Clone. The menu location can differ between Jira Cloud and self-managed Jira versions.
If you cannot see the action, check your project permissions and ask a Jira administrator whether cloning is available in your setup.
Review the clone dialog
Jira opens a form for the new issue. It may add a prefix such as CLONE - to the summary, so edit that text to make the new ticket clear.
Review the project, issue type, description, and any fields shown. Options for carrying over attachments, links, or other details depend on your Jira version and configuration.
Choose what the new issue should include
Keep only the details that apply to the new work. For example, retain a setup checklist while removing a deadline that belonged only to the original request.
If the dialog offers attachment or issue-link options, select them deliberately. A link to the original can help teammates understand the relationship, while an unnecessary link can create confusion.
Create the cloned issue
Select the create or clone button in the dialog. Jira creates a separate issue with its own issue key; the original remains unchanged.
Wait for the confirmation or new issue page before navigating away. If Jira reports an error, note the message and check required fields or project permissions.
Verify the new issue
Open the new issue and compare it with the original. Check the summary, description, assignee, priority, components, labels, attachments, and links that matter for the task.
Update the status, sprint, due date, and owner if needed. A quick comparison catches stale details before the cloned issue enters someone’s queue.
What Jira cloning copies—and what it may leave behind
A Jira clone creates a new issue using selected details from an existing one. It does not turn the original issue into a second copy or combine the two tickets.
Fields such as the summary and description are commonly included, but the exact set depends on Jira’s version, project configuration, and options in the clone dialog. Inspect the new issue rather than assuming every field transferred.
Comments, work logs, issue history, and subtasks may not be copied as part of a standard clone. If the new work needs any of these, recreate the relevant information or use an approved workflow for your Jira setup.
Before you clone: a quick review checklist
- Confirm the original: Check the issue key and make sure its instructions still apply.
- Rename the new issue: Replace a generic clone prefix with a summary that describes the new work.
- Review people and dates: The original assignee or due date may not suit the new task.
- Check project-specific fields: Components, versions, labels, and custom fields can affect routing and reporting.
- Decide whether to retain attachments and links: Carry over only items that help complete the new work.
Here's why this matters: Jira fields often drive queues, notifications, and reports. For example, an old fix version on a cloned bug can make it appear in the wrong release report.
Special cases: subtasks, linked issues, and repeated work
When the original has subtasks
Do not assume a standard clone also creates copies of every subtask. Check the new issue after creation, then create new subtasks if the work needs its own breakdown.
For a recurring launch checklist, you might clone the parent task and create fresh subtasks for testing, approval, and release. This keeps each launch’s progress separate.
When links or attachments matter
Issue links can preserve useful context, such as a dependency or a related defect. Verify the relationship after cloning because link behavior may depend on the dialog and your Jira configuration.
Attachments may contain details that apply only to the original task. Keep them only when they are relevant, accessible to the new assignee, and appropriate to share.
When the same work repeats often
Cloning works well for occasional repeats, such as opening a similar bug for another browser. If a team repeats the same workflow every week, a template or automation may reduce manual edits.
For example, a support team could use a standard issue template with required fields instead of cloning an old ticket that may contain outdated customer details.
Common cloning problems and practical fixes
- The clone action is missing: Confirm that you can view the original and create issues in the project. Ask an administrator to review permissions if the action remains unavailable.
- Jira rejects the new issue: Check required fields, field formats, and project-specific rules. Complete any missing values shown in the error message, then try again.
- The cloned ticket has stale details: Review its assignee, dates, release fields, and description before work begins. Remove anything that belongs only to the original task.
- Teammates cannot tell the issues apart: Give the clone a specific summary and add a brief explanation of how it relates to the original.
ONES.com solution: an alternative for managing issue workflows
Value proposition: ONES.com brings project management and knowledge management into one platform, with ONES Project for project work and ONES Wiki for knowledge management. The products are sold separately, so teams can choose what fits their workflow.

If you are considering a Jira alternative, ONES Project supports Jira-compatible workflows and offers deployment choices that include Cloud, On-Premise, Private Cloud, and Air-gapped environments. Its cloud and self-hosted versions have full feature parity.
Core capabilities
- Cloning creates cleanup work → ONES Project supports custom workflows and fields → Teams can shape issue processes around their needs.
- Repeated tasks require manual setup → Automation can handle recurring actions → Teams spend less time repeating routine steps.
- Sprint details need tracking → Sprint management supports planning and execution → Teams can organize work across development cycles.
- Progress is hard to assess → Built-in reporting displays project information → Leads can review delivery without assembling separate reports.
- Teams rely on many add-ons → Core project capabilities are available within ONES Project → Teams may be able to reduce plugin dependency.
- Jira workflows are familiar → Jira-compatible workflows help preserve established processes → Teams can adapt without rebuilding every workflow from scratch.
- Restricted networks limit deployment options → ONES.com supports self-hosted and air-gapped deployments → Organizations can select an environment suited to their requirements.
- Project knowledge sits apart from delivery work → ONES Wiki provides a separate knowledge management product in the same platform → Teams can select project and knowledge capabilities as needed.
Application scenarios
Software teams migrating from Jira: A team can map its issue workflow and custom fields into ONES Project, then use sprint management and reporting to continue coordinating development work.
Organizations with restricted networks: A team that cannot use a public cloud service can evaluate On-Premise, Private Cloud, or Air-gapped deployment options while retaining project management capabilities.
Teams standardizing repeated work: A delivery group can use custom workflows and automation to make recurring issue handling more consistent, reducing the need to copy and manually adjust older tickets.
Frequently asked questions
Does cloning a Jira issue change the original?
No. Jira creates a separate issue with a different issue key, and the original remains in place. Changes you make to the clone—such as updating its summary, assignee, or status—apply to the new issue. Review both tickets after cloning so teammates understand which one tracks the new work and whether a link between them is useful.
Will Jira copy comments and work logs?
A standard clone should not be treated as a full copy of the original issue’s activity. Comments, work logs, and issue history may remain only on the original. Check your new issue and Jira configuration, then add any context that is necessary for the next task. Avoid carrying over conversation details that do not apply or should not be shared.
Can I clone an issue into another Jira project?
The available destination options depend on your Jira version and configuration. If the clone dialog does not let you select another project, you may need to create an issue in the destination project and copy the relevant details manually. Confirm that you have permission to create issues there, and review project-specific fields before submitting.
Why can’t I find the Clone option?
The action may be hidden in an issue’s More menu, or your Jira interface may place it elsewhere. If it is not available, check whether you can view the issue and create issues in its project. Project permissions, custom configuration, or the Jira version can affect which actions appear. A Jira administrator can confirm what applies to your setup.
Conclusion
To clone an issue in Jira, open the right ticket, choose Clone, review the available fields and options, then verify the new issue. Pay close attention to summaries, assignees, dates, attachments, links, and project-specific fields.
A short review prevents stale details from following a task into a new cycle. When cloning becomes routine, templates, automation, or a project workflow in a platform such as ONES Project may help your team manage repeated work more consistently.