How to Clone an Issue in Jira: Steps, Tips, and Examples
Need to clone issue in Jira without losing details? Follow clear steps, tips, and examples. Read now to create a reliable copy.
Need a Jira issue for a second team, a new release, or a related piece of work? Recreating it by hand takes time and can leave important details behind.
That gets frustrating when the issue includes custom fields, acceptance criteria, or attachments that someone needs to act on. A small copying mistake can also send work to the wrong project or sprint.
To clone an issue in Jira, open the issue, choose More > Clone, adjust the new issue’s details, and confirm. The exact options can vary by Jira version and project configuration, so check the clone before sharing it. Here's why: cloning gives you a starting copy while leaving the original issue intact. I’ll walk you through the steps, explain what to check, and show when creating a fresh issue is a better choice.
How to Clone an Issue in Jira
Cloning an issue in Jira creates a separate issue with copied details, so you can reuse relevant work without changing the original. Jira typically adds a clone relationship between the two issues. You can then edit the new issue’s summary, project, fields, and other available options.
- Open the issue you want to copy. Review its summary, description, assignee, priority, and project. Confirm it is the right starting point.
- Open the issue actions. In Jira, select
More near the issue’s action buttons. Depending on your version or layout, the menu may appear under an overflow icon.
- Select Clone. If you can’t see the option, check your project permissions or ask a Jira administrator whether cloning is available.
- Review the clone details. Jira may let you change the summary and destination project or choose whether to include subtasks or other details. Available settings depend on your Jira setup.
- Make the new issue distinct. Replace old release names, dates, team references, and acceptance criteria. Add a clear summary that describes the new work.
- Confirm the clone. Create the issue, then open it and verify the fields, links, and copied content. Update its assignee and status if needed.
Example: A team completed “Add export button to billing page” for its web app. For a mobile app task, a teammate clones the issue, changes the project and summary, then rewrites the acceptance criteria for mobile behavior.
But here's the truth: cloning saves effort only when you review what carried over. An old assignee, sprint, or release name can make a new issue confusing before work even begins.

What a Jira Clone Copies—and What to Check
A clone starts with details from the original issue, which can include its summary, description, and selected fields. Jira also commonly links the new issue to the original with a clone relationship.
The exact fields and clone options depend on your Jira edition, project type, and configuration. Some projects offer options for copying subtasks or attachments; others may present a simpler dialog. Treat the clone screen as your guide, then inspect the created issue.
Check content that can become outdated
Look for references to a previous release, customer, team, date, or environment. For example, a cloned bug report may still say the problem occurs in version 4.2, even though the new issue concerns version 4.3.
Also review components, labels, fix versions, sprint assignments, and custom fields. If these values do not fit the new work, correct them before the issue enters a queue.
Confirm attachments and subtasks
Do not assume every related item was copied. Check whether the new issue has the attachments or subtasks your team needs, especially if the clone dialog offers separate options for them.
Comments and activity history may not carry over as part of a standard clone. If a decision matters to the new task, summarize it in the new description or add a link to the original issue.
Clone, Duplicate, or Create a New Issue?
Cloning works well when the new task should reuse much of an existing issue. A recurring release checklist, a similar defect report, or a follow-up task can all benefit from a consistent starting point.
A duplicate issue is usually an issue that repeats work already tracked elsewhere. If two issues describe the same bug, cloning one may create more confusion. Check whether your team should link the existing issue or close the duplicate instead.
Creating a new issue from scratch makes sense when the work only shares a broad theme with the original. For example, a request to improve checkout speed may not need the fields or steps from an unrelated checkout design task.
A quick decision test
- Clone it when the issue structure and much of the description still apply.
- Link the existing issue when both issues track the same work or depend on each other.
- Create a fresh issue when the old details could mislead the person doing the work.
Here's the practical difference: cloning gives you a prepared starting point, while a fresh issue makes you define the work from the beginning. Choose the route that needs less cleanup.
Tips for Cleaner Clones and Better Examples
Before cloning, scan the original for content that belongs only to its context. Then change the new issue’s summary and description so a teammate can understand the task without opening the old one.
For recurring work, use a well-maintained issue as your model. A team that clones a monthly maintenance task, for instance, should remove last month’s completion notes and update the target dates and system details.
Example: Reusing a bug report
Suppose a bug appears in two product areas. Clone the original report if the reproduction steps, expected behavior, and severity still apply. Change the affected component and environment, then confirm the steps work for the second area.
If the symptoms are similar but the cause is unknown, avoid copying a confirmed root cause into the new issue. Describe what you observed and keep any hypothesis clearly labeled.
Example: Starting a new sprint task
A developer may clone a task to create a similar implementation for another platform. The clone can retain useful acceptance criteria, while the developer changes the platform, testing needs, and estimate.
Be careful with sprint and release fields. A copied value can put work into a closed sprint or an outdated release, so confirm those fields before planning.
Make the relationship easy to understand
Keep the clone link when the new issue genuinely derives from the original. It gives teammates a useful path back to the earlier discussion without requiring them to guess where the new work came from.
If the connection no longer matters, explain the relationship in the description or follow your team’s linking conventions. A short note such as “Adapted for Android from the web task” can prevent mistaken assumptions.
Common Jira Cloning Problems and Fixes
Cloning is straightforward once you know where the action is and what to review. These common issues can slow you down, but each has a simple next step.
- You can’t find Clone. The action may be hidden in the
More menu, unavailable in your Jira layout, or restricted by permissions. Check another issue view or ask a project administrator to confirm access.
- The clone has the wrong project or fields. Open the new issue and correct its destination, components, versions, and custom fields. If the project is missing from a selector, request the necessary project access.
- A subtask or attachment is missing. Reopen the clone options to see whether Jira offered a copy setting. If not, create the item separately or attach the relevant material to the new issue.
- The cloned issue carries outdated information. Compare it with the intended task and replace stale dates, names, links, and acceptance criteria. Ask a teammate to review it if the original includes technical assumptions.
- The team created an unnecessary duplicate. Check for an existing issue before cloning. If both issues already exist, follow your team’s process for linking, consolidating, or closing one.
Let me explain: the most reliable fix is a short review immediately after cloning. It is easier to correct a stray sprint value before planning than after the whole team has started work.
ONES.com Solution: ONES.com
ONES.com is a unified platform for project management and knowledge management. ONES Project is its project management product and a Jira alternative; ONES Wiki is its knowledge management product. They are sold separately.

For teams reviewing their issue workflow, ONES Project offers project management capabilities that can reduce reliance on extra plugins. It supports cloud and self-hosted deployments, including on-premise, private cloud, and air-gapped environments, with feature parity between cloud and self-hosted versions.
Core capabilities
- Workflows that differ across teams: Configure custom workflows to match each team’s review and approval steps, making it easier to route issues consistently.
- Issue fields that miss team-specific context: Create custom fields for details such as affected platform or release target, helping teams capture relevant information.
- Repeated manual updates: Use automation to handle routine transitions or actions, reducing repetitive issue administration.
- Limited visibility into progress: Use built-in reporting to follow project status and identify work that needs attention.
- Sprint planning needs: Use sprint management to organize work into planned development cycles.
- Existing Jira workflows to preserve: Jira-compatible workflows can help teams maintain familiar patterns while evaluating a different platform.
- Plugin dependence: Use native capabilities for common project needs, which can reduce the number of separate plugins required.
- Restricted deployment requirements: Choose cloud, on-premise, private cloud, or air-gapped deployment to fit the team’s operating environment.
Application scenarios
A team with repeated issue patterns: A product team can configure workflows and fields around recurring defect or feature requests. Teammates can capture consistent details without relying on a collection of add-ons.
A team working in a restricted network: An organization that cannot use a public cloud service can consider ONES Project’s self-hosted deployment options. Its teams can manage project work in an environment that meets their operational requirements.
ONES Project is worth evaluating when a team needs Jira-compatible workflows alongside native project capabilities or self-hosted deployment. The fit depends on your workflow, deployment needs, and migration requirements.
Common Challenges When Cloning Issues
Old context follows the new task
Problem: A clone retains outdated project details, making the new request appear to belong to the previous release or team.
Solution: Review the summary, description, labels, versions, and assignee before assigning the work. Replace old context with details that match the new task.
Cloning creates work that already exists
Problem: Someone clones an issue without checking whether a teammate has already created the same request.
Solution: Search the project for the key terms or affected component first. If a matching issue exists, link or update it rather than creating another record.
The clone lacks necessary details
Problem: Important subtasks, attachments, or discussion points do not appear in the new issue.
Solution: Check the clone options and inspect the new issue. Add missing context directly or link to the original when teammates need its history.
People misunderstand why the issues are connected
Problem: A clone relationship appears, but teammates cannot tell whether the new issue is a follow-up, a variation, or a separate task.
Solution: Add a brief explanation in the description. State what was reused and what changed, such as “Adapted from the desktop issue for the mobile release.”
FAQs About Cloning Jira Issues
Does cloning a Jira issue change the original?
No. Cloning creates a separate issue, so edits you make to the new issue do not change the original. Jira may link the issues to show their relationship. You can update the clone’s summary, description, and available fields independently, but check its details before assigning it. That review helps prevent old context from being mistaken for current requirements.
Can I clone an issue into another Jira project?
Some Jira setups let you choose a destination project during cloning, while others may limit where the new issue can be created. The available options depend on your project configuration and permissions. If you cannot select the intended project, ask a Jira administrator to check your access. After cloning, confirm the project and issue type on the new issue.
Will Jira copy subtasks and attachments?
That depends on the clone options available in your Jira setup. Some screens may offer choices for copying subtasks or attachments; others may not. Inspect the new issue rather than assuming related items carried over. If something is missing, add it separately or link to the original issue when its details remain useful.
What is the difference between cloning and duplicating an issue?
Cloning is the Jira action that creates a new issue using an existing issue as a starting point. A duplicate is a repeated issue describing work already tracked elsewhere. A clone can be useful for similar but separate tasks; a duplicate may need to be linked, consolidated, or closed. Check whether the work is genuinely new before copying an issue.
Conclusion
To clone an issue in Jira, open the issue, select More > Clone, review the available options, and create the new issue. Then check its project, fields, subtasks, and copied context before assigning it.
Cloning can save time when a task closely resembles existing work. When details no longer apply, edit them or create a fresh issue instead. A quick review helps prevent duplicate work and outdated information.
If your team is also assessing its broader project workflow, compare the capabilities and deployment options that fit your needs. The right process keeps related work clear while giving each new issue the details it needs.