What is cloning in Jira

In project management, efficiency and accuracy are paramount. Jira, a widely used project management tool, offers a feature called “cloning” that can significantly enhance productivity. This comprehensive blog post will explore what cloning in Jira is, its various uses, best practices, and provide external resources and FAQs to help you make the most out of this feature.

What is Cloning in Jira?

Cloning in Jira refers to the process of creating a duplicate of an existing issue. This clone is an exact copy of the original issue, including its summary, description, attachments, and other fields, but it has a unique issue key. Cloning is particularly useful when you need to replicate an issue for a different project, or create a similar issue without manually entering the same information.

How to Clone an Issue in Jira

  1. Open the Issue: Navigate to the issue you want to clone.
  2. More Options: Click on the “More” button (three dots) in the issue view.
  3. Clone: Select “Clone” from the dropdown menu.
  4. Configure Clone: A dialog box appears where you can modify the summary and select/deselect elements like attachments, links, and subtasks.
  5. Create Clone: Click on “Create” to generate the clone.

Uses of Cloning in Jira

1. Duplicating Tasks for Different Teams

When multiple teams need to work on similar tasks, cloning can save time. For example, if a feature requires testing by both the QA and UAT teams, you can clone the original issue for each team, ensuring consistency in task descriptions and requirements.

2. Creating Template Issues

Cloning is ideal for creating template issues for recurring tasks. For instance, weekly reports or monthly maintenance tasks can be set up once and cloned for each new occurrence, maintaining uniformity and saving setup time.

3. Preserving Original Issues

If an issue has been resolved but a similar problem reoccurs, cloning the original issue preserves the historical data while allowing you to track the new instance separately. This helps in maintaining clear records and continuity.

4. Handling Complex Workflows

In complex workflows where an issue moves through multiple stages involving different teams, cloning helps in splitting the issue into manageable parts. Each clone can represent a different stage, ensuring that each team has a clear and focused task.

5. Facilitating Bug Tracking

When a bug affects multiple components or versions, cloning the issue ensures each instance is tracked individually. This helps in parallel debugging and ensures that fixes are applied consistently across all affected areas.

Best Practices for Using Cloning in Jira

  1. Use Clear Summaries: When cloning, modify the summary to reflect the purpose of the clone. This helps in distinguishing between the original issue and its clones.
  2. Manage Permissions: Ensure only authorized users can clone issues to prevent unnecessary duplicates and maintain data integrity.
  3. Link Clones to Originals: Use issue linking to maintain a clear relationship between the original issue and its clones, facilitating easy navigation and tracking.
  4. Avoid Over-cloning: Cloning too many issues can lead to clutter. Regularly review and clean up clones that are no longer needed.
  5. Update Clones Independently: Treat cloned issues as separate entities. Update them based on their specific context rather than assuming changes will apply universally.

External Resources

  1. Jira Software Documentation: Cloning an Issue
  2. Atlassian Community: Best Practices for Using Clones in Jira

Frequently Asked Questions (FAQs)

1. What information is copied when I clone an issue in Jira?

When you clone an issue in Jira, the following information is copied: summary, description, attachments, issue type, priority, environment, reporter, and components. You can choose to include or exclude specific elements like comments, links, and subtasks.

2. Can I clone an issue across different projects in Jira?

Yes, you can clone an issue across different projects. During the cloning process, you can select the target project and ensure that the issue type and other configurations are compatible with the destination project.

3. Is there a limit to the number of times an issue can be cloned in Jira?

Jira does not impose a strict limit on the number of times an issue can be cloned. However, it’s essential to manage cloned issues effectively to avoid clutter and maintain a clear and organized workflow.

4. How do I keep track of the relationship between original and cloned issues?

You can use issue links to maintain the relationship between original and cloned issues. Jira provides a “clones” issue link type that you can use to link the original issue with its clones, making it easy to navigate between them.

5. Can I automate the cloning process in Jira?

Yes, you can automate the cloning process using Jira automation rules or third-party plugins available in the Atlassian Marketplace. Automation can be set up to trigger cloning based on specific conditions, such as issue creation, status changes, or custom workflows.

6. Will cloning an issue copy its status and workflow?

When you clone an issue, the clone will start with the default status for new issues in the target project. It does not copy the workflow status of the original issue. You will need to transition the cloned issue through its workflow independently.


Cloning in Jira is a powerful feature that can significantly enhance productivity and streamline project management tasks. By understanding how to effectively use cloning, leveraging best practices, and utilizing available resources, you can ensure that your team maximizes the benefits of this feature. Whether you’re duplicating tasks for different teams, creating template issues, or handling complex workflows, cloning can help you maintain consistency and efficiency in your Jira projects.

Supercharge Your Collaboration: Must-Have Microsoft Teams Plugins Top 7 data management tools Top 9 project management tools Top 10 Software Testing Tools Every QA Professional Should Know 9 KPIs commonly tracked closely in Manufacturing industry