Before you start
Permissions – You must be an Administrator or hold a role with Custom Statuses rights.
Core statuses – Unexecuted, Passed, Failed are system‑locked; they cannot be edited or deactivated. Skipped cannot be deactivated if QA Copilot is enabled
1. Access the Custom Statuses page
Inside a project, open Settings → Custom Statuses. This view lists every status and lets you add, edit, deactivate, or delete.
You have full flexibility to define new statuses that suit your testing workflow.
2. Adding a New Status
Click "Create Custom Status".
Enter a Name (must be unique).
Add an optional Description.
Choose a Color.
Set a Priority.
Click Create.
The newly added custom status will be available at the time of test execution.
3. Editing an existing status
Select the row, click the Edit link, adjust any field, and Save. Historic runs stay unchanged; future runs use the update.
4. Deactivate or reactivate
Use the toggle next to the status to deactivate or reactivate it.
📝 A deactivated status won’t be available for selection at the time of test executions but will remain in logs and reports.
5. Deleting a Status
Click the Delete link on the custom status.
📝 A status can be deleted only if it has never been used. Otherwise, deactivate it instead to keep your audit trail intact.
6. Priority explained
Each custom status can be assigned a priority, which determines how the overall test case result is calculated. For example, if a test case has multiple steps with different statuses, the status with the highest priority will be applied to the entire test case. This result is then reflected in reports, dashboards, and metrics.
You can set a custom status to have a higher or lower priority than the default statuses, giving you more flexibility in how results are evaluated and displayed.
7. Control who can manage statuses
Use Roles → Permissions to grant or revoke Add, Edit, Delete Custom Statuses. That way only trusted users can change your status list.