Scope Availability

Each status can be enabled or disabled independently for different parts of the platform. Scope availability flags control where a status appears in selection dropdowns and which contexts it is valid for.

Available scopes

Scope availability is configured on the Scope tab of the status edit modal. The following scopes are currently available:

Available for Run Results

When enabled, this status can be applied to individual test run results — the outcome recorded when a test case is executed in a test run. Enable this for statuses such as Passed, Failed, Blocked, or Skipped that represent execution outcomes.

Available for Sessions

When enabled, this status can be applied to test sessions. Session statuses represent the overall state of a testing session (e.g. In Progress, Completed, Abandoned). Enable this for statuses that make sense at the session level.

Available for Scope

When enabled, this status can be used in scope-level contexts within the platform. This covers status assignments on scoped items such as test case entries within a session scope.

Automation scope

Coming in a future release. The Automation module is not yet available. The Available for Automation scope setting is reserved for upcoming automation features and has no effect in the current release. You may see this field in the status edit modal — it can be safely ignored for now.

Combining scopes

A single status can be available in multiple scopes simultaneously. For example, a Passed status might be enabled for both Run Results and Scope, while a Completed status might apply to Sessions only.

Statuses that have no scope flags enabled are still saved and visible in the admin list, but they will not appear in any selection dropdown until at least one scope is enabled.