| Features | Standard | Advanced |
|---|
Clones an entire space with or without data | | |
Data stays in your chosen region | | |
Templates that adapt to your context | | |
Reuse saved settings for future jobs | | |
Clone test plans, executions, test set and test cases | | |
Epic–story structure kept in clones | | |
Parent/child hierarchy rebuilt | | |
Built-in checks for setup issues | | |
Find and diagnose cloning errors | | |
Change field values on target issues | | |
Clone, edit and move in a single run | | |
Change issue type during cloning | | |
Respects Jira permission schemes | | |
Guided flow through each cloning step | | |
Select issues to clone via JQL | | |
Sub-tasks copied with their parents | | |
Labels carried over to cloned issues | | |
Links between issues are recreated | | |
Files on issues copied to clones | | |
Adjust links in the set before cloning | | |
Past links preserved on cloned issues | | |
Clones stay linked to originals | | |
Keep or drop original/remaining time | | |
Choose target workflow status | | |
Run clone jobs on a schedule | | |
Source issues from several projects | | |
Route each issue type to a project | | |
Choose whether comments are cloned | | |
Live status of the cloning job | | |
Add a prefix and/or Suffix to cloned summaries | | |
Allows you to Bulk Clone work items in a bundle or 1 by 1 | | |
Clones the rows you tick rather than everything your search returned | | |
Clone Work Items into a different Jira Cloud site | | |
Test steps and Test associations survive the move | | |
Trigger a Clone operation as part of a status update | | |
Fields, options and people land on their counterparts | | |
Connect a site with Atlassian sign-in — no API tokens to manage | | |
Run cross-site clones from automation rules and post functions | | |
Admins set up a site once; everyone clones as themselves | | |