The short answer
Open the ticket, select the ••• (More actions) menu, choose Clone, edit the summary, choose what to include, and select Clone. You need the Create work items permission in the space.
The clone is a separate work item. It copies most information, such as the summary and description. Attachments, subtasks, links, comments and an epic's child work items are only copied if you choose to include them. Jira adds the word "Clone" to the start of the summary and links the clone to the original.
Step by step
- Open the work item you want to copy.
- Select ••• to open the actions menu, then choose Clone.
- Edit the Summary. Remove the "Clone" prefix and say what makes this one different, for example "ID photo upload fails on iOS" instead of "Clone: ID photo upload fails on Android".
- Change the Assignee and Reporter if they should differ.
- Choose what to include (see below).
- Select Clone.
- Open the new ticket and check the description. Anything specific to the original, such as a device or a customer name, needs updating.
What gets copied
| Part of the ticket | Copied? |
|---|---|
| Summary and description | Yes |
| Most other fields | Yes |
| Attachments | Only if included |
| Subtasks | Only if included |
| Links | Only if included |
| Comments | Only if included |
| Child work items (epics) | Only if included |
| Custom fields | If set up to be cloned |
Atlassian describes the clone as copying most information from a work item like the Summary and Description fields, with the rest available to include in the dialog. Its help article describes cloning within the same space.
How the clone and the original are connected
Atlassian's help says cloned work items exist as separate entities from the original, and that their only connection is a link created when you clone. You can unlink them at any time. The link types "clones" and "is cloned by" are among the default link types, so the link shows on both tickets.
That means: editing the clone does not change the original, and moving one does not move the other. If the two pieces of work really depend on each other, add a "blocks" link as well, as described in how to link tickets.
The "Clone" prefix
Atlassian notes that the prefix "Clone" is added to the summary of a cloned work item automatically. Remove it in step 3. A board full of summaries starting with "Clone:" is hard to scan, and the word tells nobody what the work is. Space admins can use automation to remove the prefix in bulk if it has piled up.
When cloning is the right call
- The same bug on another platform. Clone the Android bug for iOS, then update the steps and device details.
- A repeating piece of work with the same checklist each time, such as a monthly report or a release checklist. Atlassian also mentions automation rules that can clone a work item on a schedule, which your admin can set up if the work repeats on a schedule.
- A template ticket your team keeps for a standard request, with subtasks included.
When to create a fresh ticket instead
- The work is only loosely similar. Editing every field of a clone takes longer than starting clean, and leftovers from the original slip through.
- The original is a duplicate report of something already known. Add a comment to the existing ticket instead of creating another.
- You want to move a ticket to another team. Cloning copies it; it does not move it, and you end up with two.
Before you clone, read the original's comments. They can hold details that the description is missing, and a clone without them starts from less than the original had.
Practise writing tickets from scratch
Cloning is quick, but knowing what a good ticket needs is what makes the clone useful. Agile Board Practice has lessons where you create a story and a bug on a practice board with the right type, priority and description, with feedback on each step. The guide to creating a ticket covers the same ground.
Frequently asked questions
How do I clone a ticket in Jira?
Open the work item, select the ••• menu, choose Clone, edit the summary, pick what to include and select Clone. You need the Create work items permission.
Does cloning a Jira ticket copy comments?
Not by default. Comments, attachments, subtasks, links and an epic's child work items are only copied if you include them in the Clone dialog.
Why does my cloned ticket start with Clone?
Jira adds the prefix Clone to the summary of a cloned work item automatically. Edit the summary to remove it and say what makes this ticket different.
Is a cloned ticket linked to the original?
Yes. Atlassian's help says the only connection is a link created when you clone, and you can unlink them at any time.
Can I clone a ticket into another space?
Atlassian's clone help describes cloning within the same space. For work that belongs to another team, ask how they want it logged.