How to Clone an Issue in Jira: Step-by-Step Process Guide
Need to reuse a Jira ticket without copying the wrong details? Learn cloning an issue in Jira step by step and avoid common mistakes. Read now.
Cloning an issue in Jira can save time when a new task needs the same details as an existing one. But a clone can also carry over fields you meant to change, or leave out information your team expects to see.
That can lead to duplicate work, confusing issue links, or a ticket assigned to the wrong person. The fix is a quick, deliberate process: choose the right issue, review what Jira will copy, and check the new ticket before you move on. Here’s how to clone an issue and avoid the common mistakes.
How to Clone an Issue in Jira
Open the issue you want to copy, use Jira’s Clone action, review the copied details, and create the new issue. Then check its fields and link to confirm the clone is ready for work.

1. Open the issue you want to copy
Find the Jira issue with details that will help you start the new task. Check its summary, description, and fields before cloning.
For example, you might use a completed “Update onboarding email” issue as a starting point for a similar update in another release. Choose an issue with useful, current details rather than one that only looks similar.
2. Choose the Clone action
Open the issue’s actions menu. In many Jira interfaces, you’ll find Clone under the More menu.
If the option isn’t visible, your permissions, project settings, or Jira version may affect what you can access. Ask a Jira administrator to check your project permissions or confirm the available workflow.
3. Review the clone settings
Jira opens a form for the new issue. Add a clear summary, review the description, and inspect any available options for copying details such as attachments or links.
The available settings can vary between Jira versions and configurations. Don’t assume every field will be copied, or that the new issue will inherit every value you see on the original.
4. Create the cloned issue
After reviewing the form, select the button to create the clone. Jira assigns the new issue its own key, such as PROJ-218, while the original keeps its existing key.
If Jira offers a destination project setting, check it before you create the issue. If you don’t see that option, your setup may require another process for creating an issue in a different project.
5. Check the new issue before work begins
Open the cloned issue and confirm its summary, description, assignee, priority, dates, and other important fields. Remove details that only applied to the original task.
For instance, a cloned bug report may still mention an old browser version. Update that description before assigning the new issue to a developer.
What Jira Copies When You Clone an Issue
Jira creates a separate issue and carries over a selection of details from the original. The exact fields and options depend on your Jira setup, so review the new issue rather than relying on assumptions.
Commonly, the clone begins with details such as the summary and description. Your Jira configuration may also offer options for copying attachments, links, or other issue information. A new issue key distinguishes the clone from the original.
Check fields that often need updating
Assignees, due dates, sprint information, versions, and custom fields deserve a close look. Some may be copied, reset, or handled differently in your project.
Imagine you clone a release task that was assigned to Maya and had a due date last month. If those values carry over, the new ticket could appear overdue and assigned to the wrong person.
Confirm links and attachments
Jira may offer an option to link the new issue to the original. That relationship helps teammates see why the new task exists and find the earlier work.
Attachments and issue links may depend on the options available in your interface. Open the new issue and verify anything your team needs before closing the original or moving on.
Cloning, Creating, and Moving Issues: What’s the Difference?
Cloning is useful when you want to start a separate issue with some existing details. Creating an issue from scratch gives you a clean start, while moving an issue changes where an existing ticket belongs.
For example, clone a recurring security check when you need a fresh task for the next release. Create a new issue when the work only resembles an earlier task. Move an issue when the same task needs to live in another project.
Choose the action that matches your goal
- Clone: Create a new issue that begins with selected details from an existing issue.
- Create: Start a new issue and enter its details without relying on an earlier ticket.
- Move: Change the project or issue type of an existing issue, subject to your Jira setup and permissions.
But here's the truth: cloning is not a shortcut around reviewing the new issue. It gives you a starting point, and you still need to confirm that the new ticket describes the work ahead.
When Cloning Helps—and When It Can Cause Confusion
Cloning works well for repeatable tasks that share a reliable structure. Examples include quarterly access reviews, standard release checks, or recurring maintenance tickets.
It can also help when a team needs a new issue that refers to an earlier investigation. Linking the clone to the original gives teammates useful context without treating both tickets as the same work.
Use a clean starting point
Before cloning, check whether the original issue still reflects your current process. An old ticket may contain outdated steps, retired labels, or a workaround that no longer applies.
For example, a previous release task might refer to a testing environment your team has replaced. Cloning that issue without updating its details can repeat old mistakes across several releases.
Keep the new task distinct
Give the clone a specific summary and update details that describe the new work. If the original task is still active, add context explaining how the two issues relate.
Here's why: a clear title helps teammates tell similar tickets apart in a queue. “Review checkout permissions for May launch” is easier to act on than another ticket titled “Review permissions.”
How to Troubleshoot Common Cloning Problems
If cloning fails or the new issue looks incomplete, check the action, permissions, project configuration, and copied fields. Small differences between Jira environments can change what you see.
Clone isn’t available
First, confirm that you have permission to create issues in the project. If you do, ask a Jira administrator whether the Clone action is enabled or available in your interface.
Important details didn’t carry over
Compare the original and new issues field by field. Your project may not copy every custom field, attachment, or relationship automatically.
If a required field is missing, enter it manually or ask an administrator whether the project configuration can support your team’s cloning process.
The clone appears in the wrong place
Check the project name and issue key on the new ticket. If you need an issue in another project, look for a destination option in the clone form.
When that option isn’t available, ask your Jira administrator about the approved cross-project process. The right steps can depend on project configuration and permissions.
A Project Management Alternative for Repeatable Issue Work: 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 a Jira alternative; ONES Wiki provides knowledge management and is a Confluence alternative. They’re sold separately.

If your team is reviewing how it manages repeatable work, ONES Project offers project controls that can help organize issues and workflows. Its deployment options include Cloud, On-Premise, Private Cloud, and Air-gapped environments, with feature parity between cloud and self-hosted versions.
Core capabilities: common project needs and practical responses
- Repeated issue patterns: Teams need a consistent way to manage recurring work. ONES Project supports custom workflows and fields, helping you represent work in a structure that fits your process.
- Jira workflow familiarity: Teams moving from Jira may want familiar workflow practices. Jira-compatible workflows help make that transition easier to understand.
- Limited visibility into progress: Teams may need to check status across active work. Built-in reporting provides a way to review project progress without relying on extra reporting add-ons.
- Sprint coordination: Agile teams need to plan and track work within sprints. Sprint management supports organizing and reviewing sprint activity.
- Manual handoffs: Repetitive steps can slow down issue handling. Automation can reduce routine work by applying configured actions to workflow events.
- Plugin overhead: Extra plugins can add setup and maintenance work. Native project capabilities can reduce plugin dependence for teams whose needs match the built-in functions.
- Restricted deployment requirements: Some teams need to host their project environment themselves. On-Premise, Private Cloud, and Air-gapped deployment options support different infrastructure requirements.
- Small-team evaluation: A team may want to try the platform before making a broader decision. The free plan supports up to 30 seats.
Application scenarios
A team standardizing recurring work: A release team can define custom workflows and fields for its recurring checks. Reporting and sprint management can help the team track those issues across planned work.
A team working in a restricted environment: An organization with specific hosting requirements can assess the self-hosted deployment options. It can compare those options with its infrastructure and security needs before choosing a setup.
The right fit depends on your team’s workflow, hosting needs, and project requirements. You can assess ONES Project as a Jira alternative if you’re reviewing how your team manages repeatable work.
Common Challenges When Cloning Jira Issues
Cloning is straightforward once you know what to check. These common problems can still create extra work if you overlook them.
- Outdated details appear in the clone. The original issue may refer to old steps, dates, or environments. Review the description and replace any details that don’t apply to the new task.
- The new issue has the wrong assignee or priority. Check ownership and priority before assigning work. Update them to reflect the new task rather than the original ticket.
- Teammates can’t tell why two issues are related. Use an available link to connect the clone to the original, then add a brief explanation to the new issue.
- A required field is missing. Check the project’s required fields and the new issue’s configuration. Enter missing information or ask an administrator to review the setup.
- The team clones too many issues. Cloning every similar task can carry old details into new work. Use it when the original provides a useful starting point, and create a fresh issue when it doesn’t.
Frequently Asked Questions
Does cloning an issue in Jira change the original?
No. Cloning creates a separate issue with its own key, so the original remains a distinct ticket. However, copied information may appear in both issues. Review the new one for fields that need different values, such as the assignee, dates, summary, or description.
Can I clone an issue into another Jira project?
That depends on the options available in your Jira environment. If the clone form includes a destination project setting, select and verify the project before creating the issue. If it doesn’t, ask a Jira administrator about the approved process for creating or moving work between projects.
Does a cloned issue include comments and attachments?
What Jira carries over can depend on your version and configuration. Some clone forms provide options for copying attachments or other details, while comments may not be carried over as part of the standard clone process. Review the form and check the finished issue to confirm what your team needs.
Why can’t I see the Clone option in Jira?
Your permissions, project settings, or Jira interface may affect whether the action appears. Confirm that you can create issues in the project. If you still can’t find Clone, ask a Jira administrator to check the project configuration and your access.
Should I clone an issue or create a new one?
Clone an issue when its structure and details provide a useful starting point for separate work. Create a new issue when the task only resembles the earlier one or needs a clean description. Either way, give the ticket a clear summary and review its fields before assigning it.
Conclusion
Cloning gives you a quick starting point for repeatable Jira work. Open the right issue, use the Clone action, review the available settings, and check the new ticket before work begins.
But here's the truth: the clone is only helpful when its details match the new task. Update outdated fields, confirm links and attachments, and make the relationship between the issues clear. With that final review, cloning an issue in Jira can save time without carrying yesterday’s mistakes into today’s work.