Editing & Managing

Once a test case exists, you can update its fields, switch its template, manage attachments and linked issues, or delete it entirely. This page covers the day-to-day operations for keeping your test cases accurate and up to date.

Editing a test case

You edit a case by changing it. There is no Edit button, no edit mode, and no Save button — open a case in the side panel or full page, click the thing you want to change, and change it.

A ✓ Saved receipt flashes as each change lands. Leaving the case — closing the panel, opening it full page, switching cases, or closing the tab — commits anything still pending first.

Made a mistake? Press ⌘Z. Undo works across your edits to a case, and ⌘⇧Z redoes. Inside a text field it defers to your browser’s own text undo, so you never lose a half-typed sentence to an over-eager shortcut.

Editing requires the Edit test cases permission. Without it the case opens read-only. Commenting is separate — view access is enough.

What you can edit

• Title — update the case name.
• Folder — this is how you move a single case.
• State — transition the case (e.g. Draft → Ready → Approved).
• Estimate — adjust the time estimate.
• Labels — add or remove tags.
• Template fields — any field your template defines, including rich text, dropdowns, and steps.

The case number cannot be changed — it is permanently assigned at creation.

Changing the template

The template is a property row like any other, so switching is a click. This is useful when your testing approach changes or a template is updated.

Changing a template can lose field values. Fields shared by both templates keep their values; a field the new template does not have has nowhere to store one. If you switch by mistake, ⌘Z reverses it within your session.

Managing attachments

Case attachments are available on both surfaces — in the side panel below the properties, and in the rail on the full page. Files attached to a custom field are listed alongside them, grouped by field.

• Add — click Add file, or drag files onto the drop area. Supported: PNG, JPG, GIF, WebP, PDF, CSV, Excel, Word, PowerPoint, and plain text.
• Remove — click the × beside an attachment and confirm in the dialog that follows.
• Inline images — paste or drag images directly into rich text fields and step cells. These are embedded in the field content.

Removing an attachment cannot be undone. A confirmation dialog names the file first — it opens with Cancel focused, Enter confirms and Esc keeps the file — but once confirmed there is no restore. Unlike a step deletion, ⌘Z will not bring it back, so download anything you might still need before removing it.

Removing an attachment does not affect completed test runs. If the case was already executed, the run keeps its own snapshot.

Managing linked issues

Link tracker items to provide traceability between test cases and the features or bugs they cover. See Case Detail for the full walkthrough, and External References for connecting a tracker.

Linked issues can be used as a filter in Browsing & Search — including Unclassified links, which finds cases carrying a link nobody has given a relation to.

Bulk actions

Select several cases and the bulk bar appears with the count, an Add to run button, and an Actions palette offering:

• One entry per bulk-editable field — set a field across the whole selection at once. Each list opens with a clear option (for a Priority field, No Priority) to empty the value rather than set one.
• Move to folder… — the way to move many cases at once. It lists the folders you made; Unfiled is not offered as a bulk destination, so unfiling cases is a one-at-a-time change on the case’s own Folder property.
• Add label… and Remove label…, when the project has tags.
• Copy IDs and Export CSV — available to every role.
• Delete, if you have permission.

A multi-select field is replaced, not appended to. Setting one in bulk writes the whole value, so cases that previously had other options selected lose them.

Undoing a bulk change

A bulk write lands on hundreds of rows at once, so every one of them — setting a field, Move to folder, Add label, Remove label — comes back with a way out.

• A toast with an Undo button appears at the bottom of the screen, reading what happened and what the server actually did: 12 cases · Priority → Low, then 12 of 14 cases updated · 2 already matched. It clears itself after about eight seconds. If the write failed it stays, in an error tone, offering Retry instead.
• A N bulk changes · reversible pill sits in the same place once the toast is gone. Open it and you get a Bulk changes panel listing every bulk write you have made, newest first, each with who made it, how long ago, and a Revert button. A reverted entry greys out and reads reverted.

Undo on the toast and Revert in the panel are the same entry, so using one and then the other does nothing the second time.

The history lasts for your browsing session. It holds up to 50 entries and is dropped when you reload the page or leave the project. It is a fast way back from a mistake you just made, not an audit trail.

⌘Z does not reach bulk writes. Undo drives your edits to a single case; the dock drives bulk. That split is deliberate — one stray keystroke should never quietly reverse five hundred rows — so reach for the toast or the pill instead.

Bulk delete is the exception: no Undo, no ledger entry. There is no restore path behind it, so the confirmation dialog carries the whole weight of the decision. It always confirms, whatever the count.

Export CSV covers the rows currently loaded — the columns are Case, Title, Status, Template, Last result, Created by, and Updated. The first column holds the canonical reference (C-78), not a bare number; a case still saving has no reference yet, so its cell is left empty rather than filled with a wrong one. The file is UTF-8 and named test-cases-YYYY-MM-DD.csv. If you used Select all matching this filter without scrolling through the results, scroll first or narrow the filter. Bulk delete is switched off entirely for a select-all-by-filter selection: it will not destroy a set you have not seen.

Copy IDs puts canonical references on the clipboard — C-1, C-215 — in the order you selected them. Cases that have not finished saving have no reference yet and are left out; the toast counts what actually landed, so 8 case IDs copied · 2 not saved yet means what it says.

Scripting against the export? The first column header is Case and holds C-78. It used to be ID holding a bare database number, which is exactly how a primary key ended up being read as a case number — the rename was the fix. A spreadsheet or script keyed on the old header needs updating.

Deleting a test case

Open the case in the side panel or full page and choose Delete case from the Case actions menu. To delete several at once, select them and use Delete in the bulk actions palette.

A confirmation dialog always appears, whatever the count. It opens with Cancel focused, so an accidental Enter does nothing destructive. Delete and Backspace on a selected row deliberately do nothing at all.

Deletion is permanent and there is no undo. TestOrchestrator has no trash, no recycle bin, and no restore for a deleted test case — unlike every other action on this page, deletion is not covered by ⌘Z. The case is removed from the repository and taken out of any active, non-closed runs. Recovering one is a support and database matter, not something you or an administrator can click.

Permissions reference

The following permissions control editing and management operations:

For a complete permissions overview, see Test Cases Overview.