Scope Availability
Each status can be switched on or off independently for the parts of the platform it may be selected in. These switches live in the Available in panel of the status editor, and the Statuses list shows the result in its Available in column.
The three places
The panel offers three switches. Each says what it does under its own label:
| Switch | What it controls |
|---|---|
| Test runs | Selectable when recording a run result. Switch this on for the outcomes a tester records against a case in a run — Passed, Failed, Blocked, Skipped. |
| Explorations | Selectable in exploratory sessions. Switch this on for statuses that make sense on an exploration and on the results logged inside one. |
| Automation | Accepted from CI and API result submissions. |
There is no Automation section to browse. The workspace settings rail has no Automation entry — the switch marks a status as one an automated submission may use, rather than opening an area in the app.
Combining them
A status can be available in more than one place at once. A Passed status is usually on for all three; a Debriefed status might be for explorations only. Where all three are on, the list reads Everywhere; otherwise it names the ones that are.
A status available nowhere cannot be saved. Switch all three off and the panel warns “A status available nowhere cannot be selected by anyone. Turn on at least one.”, and the save button on the bar at the foot of the page goes out of reach with the same reason on hover.
Untested is available everywhere and the three switches are locked on it — see System and protected statuses.