On this page:

Checklists in cloned issues

Our checklist replication feature enhances the cloning experience in Jira, providing users with the ability to maintain consistency in their workflows while offering the flexibility to adapt checklists to the unique requirements of each task.

The ... menu open in a Jira issue with the clone button selected.
The ... menu open in a Jira issue with the clone button selected.

Cloning with checklist inclusion

When a Jira user clones an issue containing a checklist, a new issue is created with the checklist automatically included.

The behavior of a checklist when the Jira issue is cloned
The behavior of a checklist when the Jira issue is cloned

Unchecked checkboxes

The cloned checklist will feature all checkboxes unchecked, irrespective of their state in the original checklist. This ensures that users can begin anew without any pre-existing progress influencing their workflow.

The behavior of a checklist with unchecked tasks when a Jira issue is cloned.
The behavior of a checklist with unchecked tasks when a Jira issue is cloned.

Ad-hoc checklist preservation

If the original issue featured an ad-hoc checklist, the cloned issue will also include the same checklist.

The behavior of an ad-hoc checklist when a Jira issue is cloned.
The behavior of an ad-hoc checklist when a Jira issue is cloned.

Template checklist duplication

In cases where the original issue’s checklist was created from a template, the cloned issue duplicates the checklist, potentially differing from the state of the template.

The behavior of a checklist template when a Jira issue is cloned.
The behavior of a checklist template when a Jira issue is cloned.

No conflict with default templates

The feature seamlessly integrates with default templates set in the issue settings. In cases where a linked template exists, it will be utilized for the cloned checklist, overriding any default template conflicts.

The behavior of the default checklists when a Jira issue is cloned.
The behavior of the default checklists when a Jira issue is cloned.

Any project automations that trigger on “Issue created,” will override the checklist when you clone a Jira issue. This is because automation acts after the issue is created.

Behavior with multiple checklists

When cloning a Jira issue that has multiple checklists associated with it, all of those checklists will get duplicated to the cloned issue and any tasks that have been completed or skipped will be wiped.

The behavior of the default checklists when a Jira issue is cloned.
The behavior of the default checklists when a Jira issue is cloned.

Link to this page: https://seibert.biz/diditcloningissues