Staged Test Cases
A staged test case is one you have written in the Add Case dialog but not created yet. Staging lets you write several cases over one or more sittings, review them, and add them to the repository together when they are ready.
Staged cases are private. Only the author can see, open, rename, or delete one, and there is no administrator override. A staged case is not a test case: it has no ID or version, and nothing in it appears in the repository, search, reports, dashboards, test runs, exports, the API, the audit log, webhooks, or notifications until it is created.
Staging a test case
In the Add Case dialog, click Stage Case instead of Create. The case is staged under its name and the dialog closes. If the case has no name yet, you are asked for one, and it becomes the test case's name. A case can be staged with other required fields still empty; they only block creation. Reopening a staged case and staging it again updates the same entry.
Files you have selected but not yet uploaded are not part of a staged case. Attach them after the case is created.
Test cases produced by AI test generation can be staged too: on the wizard's review step, Stage saves the selected cases as staged cases instead of importing them. Each one opens in the Add Case dialog like any other staged case, with the generated field values, steps, tags, and source-issue link already filled in.
The automatic recovery of unsaved changes that protects you from an interrupted session is separate from staging and keeps its own 30-day retention. Staged cases are kept until you create or delete them.
My Staged Cases
My Staged Cases in the repository actions lists your staged cases for the project, with a count badge. Each entry shows its name, target folder, and when it was last updated.
- Open a staged case (click it) to review or change it in the Add Case dialog. Create there creates that one case and removes it from the list.
- Rename (which renames the test case) or Delete a staged case from its menu. A deleted staged case is removed from the list; it was never created, so nothing else changes.
- If you have staged cases in other projects, the bottom of the list names those projects with their counts; each name opens that project's repository with its staged cases shown, so nothing you staged is out of reach.
- A staged case that cannot be created as it stands shows a problem count; hover it to see why. This happens when its folder was deleted, its template is no longer assigned to the project, its state no longer exists, or a required field is empty. Open it to fix it.
Creating several at once
Tick the staged cases you want (Select All ticks every one that has no problems) and click Create selected. The cases are created in list order, each in its own target folder, exactly as the Add Case dialog would create them: the same template, field values, tags, linked issues, steps, and first version, and the same review gate rules for the chosen state. Entries with problems are left out.
Each created entry is removed from the list. One that could not be created stays in the list with the reason, so you can open it, fix it, and try again.
Where staging is recorded
A test case created from a staged case shows Staged At, the time it was staged, next to Created At on its details page. The same value is part of the case's creation entry in the audit log, so a reviewer can tell a staged case from one created directly. A test case created without staging has no Staged At.