Managing Statuses

The Statuses page in Settings → Statuses lets Tenant Admins and Project Admins create, edit, delete, and enable or disable all workspace statuses.

Creating and editing statuses needs Starter. On Free, every status stays visible and can be recorded on results. The row actions are removed, New status carries a lock and a Starter chip — a billing admin’s click opens the plan, anyone else’s sends an upgrade request — and the status editor opens read-only. A note under the panel heading says so; after a downgrade it says that every status stays selectable on results. See Plans and Billing.

Browsing and searching statuses

The Statuses page lists every status in the workspace. The search box filters by name, system name or alias. Each row carries six columns:

There is no sort control, no bulk selection and no reordering on this page; the list is ordered by display order and then by name.

Row actions

Every row carries the same three-item menu under the button at the end of the row. Items that do not apply to that status are greyed out rather than hidden, and hovering one says why.

Creating a status

1. Click New status. This opens the status editor as its own page — it is not a dialog, so the URL is linkable and the browser Back button works.
2. Under Identity, pick an icon and colour and enter a Name. Appears as, beside the two controls, previews the result.
3. The System name fills itself in from the name — lowercase letters, numbers and underscores, starting with a letter. You can edit it before saving; it is permanent afterwards.
4. Optionally add Aliases, comma-separated. They are accepted by the API and by automation.
5. Under Meaning, choose the Outcome and whether the status Counts as a completed result.
6. Under Available in, switch on the places the status may be selected.
7. Under Projects, leave All projects or switch to Selected projects and choose them.
8. Click Create status on the bar at the foot of the page.

The save bar only appears once something has changed. It names what you are saving, offers Discard when you are editing an existing status, and stays out of the way until then. Leaving the page with unsaved changes asks first.

System names are derived, and tidied as you type. Capitals are lowered and anything else becomes an underscore; a name that would not start with a letter is prefixed s_. Typing “2026 Regression Watch” produces s_2026_regression_watch.

Two saves the editor refuses

Both guards leave the save button in place but out of reach, with the reason on hover, and the sentence itself sits in the panel that owns the offending control:

• Available nowhere. With all three Available in switches off, the panel warns “A status available nowhere cannot be selected by anyone. Turn on at least one.”
• Selected projects, none chosen. The Projects field reads “Choose at least one project, or this status appears nowhere.”

Editing a status

Click the status name, or Edit status… in the row menu, to open the same page-level editor. Everything except the system name can be updated.

System name is permanent. Once a status is created, its system name cannot be changed — the field reads “Fixed after creation — integrations depend on it.” If you need a different identifier, create a new status.

Untested explains its own limits. Opening Untested shows one banner at the top of the editor: “Untested is protected: it is how an unrecorded result is represented, so only its name, aliases, icon and colour can change. It stays enabled, available everywhere, and on all projects.” The locked controls stay on screen and carry the same reason on hover.

A link to a status that no longer exists says so. A bookmarked editor URL for a deleted status answers with “That status does not exist” and a way back to the list, rather than waiting.

Enabling and disabling a status

Use Enable status / Disable status in the row menu. Disabled statuses are hidden from users throughout the platform but their historical data is preserved, and you can re-enable one at any time. The confirmation toast carries an Undo, because undoing this is the same write with the previous value.

Untested cannot be disabled. The Untested status is permanently enabled — it is the state every case starts a run in, so disabling it would leave unrecorded results with nothing to say. The menu item is greyed out with that reason.

Deleting a status

Choose Delete status… from the row menu. What you are asked depends on whether anything has been recorded against the status.

When nothing uses it, the dialog says so — “Nothing uses this status yet, so it can be removed cleanly” — and warns that this cannot be undone: a status cannot be restored, and re-creating it would need a different system name.

A status in use is replaced, not just deleted. The dialog counts the records that would be left without a status and makes you say what they become. The counts are shown as a table — Test run cases, Test runs, Explorations, Exploration results — and Reassign and delete stays out of reach until you have picked a replacement. Every record listed moves to the status you choose.

Only statuses that are still enabled, and that are available in the places the affected records need, are offered as replacements. If nothing qualifies, the dialog says so instead of offering a dead button — create a suitable status first.

Neither delete can be undone. Unlike enable and disable, a deletion carries no Undo in its toast.

System statuses cannot be deleted. Statuses built into the platform are protected from deletion; Delete status… is greyed out on their rows. You can disable them instead.