Just a heads up: On March 24, 2025, starting at 4:30pm CDT / 19:30 UTC, the site will be undergoing scheduled maintenance for a few hours. During this time, the site might be unavailable for a short while. Thanks for your patience.

×
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

How to manually clone a ticket

Jeff Donnelly
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 6, 2024

I would like to clone a ticket already created in the software

3 answers

1 accepted

3 votes
Answer accepted
Rebekka Heilmann _viadee_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
February 6, 2024

Hi @Jeff Donnelly 

check out the official documentation: Clone an issue | Jira Software Cloud | Atlassian Support

0 votes
Julie d_Antin _Elements_
Atlassian Partner
March 4, 2025

Hi @Jeff Donnelly , great question!

If you need to manually clone a Jira ticket, there are a couple of ways to do it, depending on your needs.

Option 1: Native Jira cloning

Jira provides a built-in cloning feature that allows you to duplicate an issue:

  1. Open the issue you want to clone.
  2. Click the More (•••) button in the top-right corner.
  3. Select Clone from the dropdown menu.
  4. Update any necessary fields in the clone dialog.
  5. Click Create to generate the new issue.

Limitations of native cloning:

  • Attachments and comments are not copied by default.
  • Issue links are not retained, meaning you will need to manually re-link related issues.
  • No automatic synchronization—if details in the original issue change, the clone will not update.

Option 2: Automating cloning and synchronization with Elements Copy & Sync

If you need more flexibility, automation, or synchronization, Elements Copy & Sync is a powerful solution that goes beyond basic Jira cloning.

With preconfigured recipes, you can:

  • Automatically copy issues based on workflow transitions or user actions.
  • Clone issue fields, attachments, and comments seamlessly.
  • Preserve issue links to maintain context.
  • Bulk copy issues - perfect for large-scale operations.
  • Keep issues in sync so updates on the original issue reflect in the clone.

Example use cases:

  • Escalating a Jira Service Management ticket to development while keeping both issues synchronized.
  • Cloning an epic with all its linked stories and subtasks for consistent project setup.
  • Duplicating issues across multiple projects while ensuring updates are reflected everywhere.

Learn more about setting up a copy recipe.

Let me know if you have any specific requirements—I would be happy to guide you through it.

0 votes
Luka Hummel - codefortynine
Atlassian Partner
February 7, 2024 edited

Hi @Jeff Donnelly

Here's a general guide on how to manually clone a ticket in Jira.

Steps to Manually Clone a Ticket in Jira:

  1. Open the Ticket: Navigate to the ticket that you want to clone.
  2. Clone the Ticket:
    Look for the Actions menu ··· in the ticket's menu options.
    Click on it, and then select Clone from the dropdown list.
  3. Configure the Clone:
    You will also be prompted to enter a summary for the new ticket. You can modify it to distinguish the cloned ticket from the original.
  4. Create the Clone:
    Once you have configured the clone to your liking, click the Create button to finalize the process.
  5. Adjust the Cloned Ticket:
    After the cloned ticket is created, you might want to make further adjustments that weren't covered in the cloning process, such as changing the assignee, adjusting labels, or updating any custom fields.

Additional Tips:

  • Bulk Cloning: If you find yourself needing to clone tickets frequently, consider looking into automation tools or plugins that can streamline this process. For instance, our app Deep Clone for Jira allows for bulk cloning and provides more granular control over what gets cloned, saving time and effort for repetitive tasks.
  • Customization and Automation: Explore the possibility of automating repetitive tasks within your project management software. Apps and add-ons can significantly reduce manual work and improve consistency across your projects.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
atlassian, atlassian government cloud, fedramp, webinar, register for webinar, atlassian cloud webinar, fedramp moderate offering, work faster with cloud

Unlocking the future with Atlassian Government Cloud ☁️

Atlassian Government Cloud has achieved FedRAMP Authorization at the Moderate level! Join our webinar to learn how you can accelerate mission success and move work forward faster in cloud, all while ensuring your critical data is secure.

Register Now
AUG Leaders

Upcoming Jira Events