Clone & Bulk Operations

Clone test cases and perform bulk updates, moves, and deletions across your test suite.

Clone

Cloning creates an exact duplicate of an existing test case, saving you time when you need to create similar test cases with minor variations (e.g., the same login flow but with different user roles or input data).

How to clone a test case

In the test case table, select exactly one test case with its checkbox.
Click Clone () in the table toolbar. Clone is disabled when nothing is selected, when two or more rows are selected, and while Select All is active.
A new test case is created with the title Clone - [original title] and a new ID.

There is no Clone button on the test case detail view — cloning is done from the list.

What gets copied

The clone is a copy of the whole test case row, so every stored field comes across:

Title (prefixed with "Clone - ")
Summary and Preconditions
Priority, Status, Automated flag
Labels, Environment, Features, Platform
Test Data and Expected Result
Owner
The current version number
All test steps, in the same order, including their Test Data
Folder assignment
Custom field values

What does NOT get copied

Test Case ID — The clone receives a new, unique ID (e.g., TEST-456)
Automation IDs — Automation mappings stay on the original test case only. Clone a test case that reports from CI and you must map the clone's automation IDs yourself.
Execution history — The clone starts with no execution records
Change history — The clone's history starts fresh, with a single entry recording that it was cloned
Defect links — No defects are carried over from the original
Attachments — Files attached to the original are not copied to the clone

After cloning, remember to update the title and any fields that need to differ from the original. The clone is fully independent — changes to the clone do not affect the original, and vice versa.

Bulk Operations

When you need to update, move, or delete many test cases at once, bulk operations save significant time compared to editing each test case individually.

Selecting test cases

Use the checkboxes on the left side of the test case table to select individual test cases. The checkbox in the table header selects every test case on the current page.

When a full page is selected, a Select All (N) link appears in the toolbar. Clicking it extends the selection to every test case matching your current filters, search and folder — across all pages — and the toolbar switches to showing Clear All. Bulk Edit, Delete, Archive and Export then apply to that whole set, not just the visible page.

Available bulk actions

Once you have selected one or more test cases, the bulk action toolbar appears with the following options:

Action	Description
Archive ()	Sets the status of every selected test case to Archive. They move to the Archive view in the sidebar.
Clone ()	Enabled only when exactly one test case is selected. See Clone above.
Delete ()	Permanently delete all selected test cases. A confirmation dialog will ask you to verify this action.
Bulk Edit ()	Enabled from two selected test cases upward. Pick one visible field — for example Priority, Status, Automated, Labels, Environment, Platform, Features, or a custom field — set the new value, then apply. With one row selected the same button opens the normal edit form instead.

Folder, Owner, Requirements, Defects and Automation IDs cannot be bulk-edited — they are excluded from the Bulk Edit field list, and hidden fields are excluded too.

There is no Move to Folder bulk action. To move test cases between folders, select the rows and drag any selected row onto a folder in the left sidebar. See Folders & Organization.

Bulk delete is irreversible. Deleted test cases cannot be recovered. Their execution history, change history, defect links, and attachments are also permanently removed. If you are unsure, consider changing the status to Archive instead of deleting.

The table shows a fixed 20 test cases per page, so to act on more than 20 at once, tick the header checkbox and then click Select All (N) rather than repeating the operation page by page.