The Duplicate action creates a fresh copy of a test case or a suite subtree. A suite duplicate recreates every descendant suite and deep-clones every case they contain. The copy can land in the same project and suite, a different suite, or a completely different project in your organization.
Reaching the duplicate modal
- Test case — open a case’s detail panel and click the duplicate icon (⧉) in the header row.
- Suite — in the repository tree, click the duplicate icon on the suite’s path bar.
Both entry points open the same Duplicate modal.
The duplicate modal
- Destination project — defaults to the project you’re duplicating from, but lists every project in your organization, each with its avatar. Cross-organization duplication is never possible.
- Destination suite — duplicating a case defaults to that case’s own current suite (or Project root if the case has no suite); duplicating a suite defaults to Project root. Changing the destination project always reloads this selector against the newly chosen project and resets it to Project root — even if you switch back to the original project.
- Prefix — optional. Leave it empty for an exact copy with no marker of any kind. Type a prefix (for example
Copy of) and it is prepended to the top-level title only:- Duplicating a case prepends the prefix to the case title.
- Duplicating a suite prepends the prefix to the root suite’s name only — every descendant suite and every case inside keeps its exact original name/title.
- Clone strategy — suites only. Choose Cases and suites (the default) to duplicate the suite hierarchy together with every case it contains, or Only suites to duplicate just the suite hierarchy with no cases, steps, attachments, or custom field values (nothing is copied to storage and no case count is used).
Click Duplicate to commit. On success the modal closes, a confirmation toast appears, and the destination project’s suite/case tree refreshes so the copy shows up immediately — you stay on the page you were on, there is no navigation to the new copy. On failure the modal stays open with an error toast so you can adjust the fields and retry.
What gets copied
Duplicating a test case copies:
- Title (with the optional prefix, top-level only), description, and tags.
- Every step, in order, with its action/data/expected text.
- Every step attachment — each image is copied to a brand-new file, never shared with the original.
- Custom field values.
Duplicating a suite additionally recreates every descendant suite. Duplicated suites are always created fresh — if the destination already has a suite with the same name, a new sibling is created; the existing one is never merged into or reused.
When you duplicate a suite, archived cases inside it are skipped — only active cases are copied, so archived cases never reappear as active duplicates (duplicating a single case directly still copies that case regardless of its archived state). Choosing the Only suites clone strategy skips cases entirely, regardless of archived state — only the suite hierarchy is recreated.
Same-project vs. cross-project rules
- Milestone — kept when the destination is the same project as the source; dropped when the destination is a different project (a milestone belongs to one project, so it cannot follow a case across projects).
- Custom field values — copied as-is within the same project. Across projects, only values for fields that apply to the destination project carry over; values for fields the destination project doesn’t use are dropped.
- Tags — always copied exactly as they are, in every case.
What is never copied
Duplicating a case or a suite never copies:
- Run history or results.
- Comments or comment attachments.
- Defect links.
A duplicate is a fresh starting point for authoring — not a snapshot of a case’s testing history.
Size limit
A single duplicate request is capped at a maximum number of cases and a maximum number of step attachments. If a suite subtree you’re duplicating exceeds either limit, the request is rejected before anything is written or copied, and the modal shows an error explaining which limit was hit.
Duplicating a multi-selection (bulk duplicate)
Select several suites and/or standalone cases at once in the repository tree — the multi-selection bar’s Duplicate button opens a dedicated bulk-duplicate dialog for the whole selection in one request.
- Destination — same as the single-item modal: any project in your organization, with a destination-suite selector that reloads and resets to Project root whenever you change the project. A
null/root destination is always allowed. - Clone strategy — three options instead of two:
- Cases and suites — duplicates every selected suite’s hierarchy and cases, plus every standalone selected case.
- Only cases — duplicates every selected case flat into the destination, ignoring suite structure entirely (even if suites were also selected).
- Only suites — duplicates only the selected suites’ hierarchies, with zero cases, steps, attachments, or custom field values — mirrors the single-suite Only suites strategy, applied to every selected suite at once.
The whole selection is cloned as one all-or-nothing request: if the combined case count, suite count, or attachment count across the mixed selection exceeds the size limit, the entire request is rejected before anything is written or copied — there is no partial bulk duplicate. On success the destination project’s suite/case tree refreshes, your original multi-selection clears, and a single confirmation toast reports how many cases and suites were duplicated. On failure the selection is preserved so you can adjust it and retry.
Permissions
Duplicating requires member-level access or above. Viewers do not see an enabled duplicate button.