Managing Runs

Day-to-day operations for active and completed test runs — editing metadata, assigning tests to team members, closing completed runs, reopening them when needed, and deleting runs you no longer need.

Editing a run

To edit a run, click the three-dot menu on the run row in the table and select Edit, or open the run detail page and click the Edit button on the Status tab.

The Edit Run modal is identical to the Create Run modal. You can change:

• Title — rename the run
• Cycle — reassign to a different sprint, release, or iteration
• Lifecycle State — move the run to a different state
• Environment — change the platform combination
• Tags — add or remove labels
• Notes — update the rich-text briefing on the Notes tab
• Case selection — add or remove test cases from the run

Click Save to apply changes. Editing a run requires the Create test runs permission.

Assigning tests

Assigning distributes test cases across your team so each tester knows which cases are theirs.

1. Click the three-dot menu on a run row and select Assign Tests, or open the run detail page and click Assign.
2. Choose the assignment scope:
   • All cases — assign every case in the run to the selected user.
   • Selected cases — open the case selection modal to pick a subset of cases.
3. Select a User from the dropdown.
4. Click Assign.

Assigned cases show the user's avatar in the Assigned To column of the results table. Assigning tests requires the Execute tests permission.

Closing a run

Closing marks a run as complete. Before the run is closed, TestOrchestrator checks for potential issues.

1. Click Close Run from the three-dot menu or the run detail page.
2. The close guard checks whether any cases have a failed result with no linked external issue (defect). If any are found, a warning dialog appears.
3. The dialog lists the affected cases and offers two options:
   • Review results — return to the run to link defects or re-test.
   • Close anyway — proceed with closing despite unlinked failures.
4. If no issues are found, or you choose Close anyway, the run is closed.

Why the close guard exists. The guard ensures traceability — every failure should be linked to a defect so the team can track resolution. Closing a run with unlinked failures is allowed but flagged as a conscious decision.

What closing means

• The run moves to the Closed lifecycle and appears under the Closed toggle on the runs list.
• Results can no longer be recorded — the run becomes read-only.
• All existing data (results, comments, attachments, issue links) remains fully accessible.
• The run continues to appear in summary statistics and activity timelines.

Reopening a run

To reopen a closed run, edit it and change the Lifecycle State back to an active state (e.g. In Progress). The run reappears in the Active view and accepts new results immediately.

Reopening preserves all existing data. No results, comments, or issue links are lost.

Deleting a run

To delete a run, click the three-dot menu and select Delete. A confirmation dialog appears — click Delete to confirm.

Deletion is permanent. Deleting a run removes the run and all its recorded results, comments, attachments, and issue links. This action cannot be undone.

Permissions reference

For a complete permissions overview, see Test Runs Overview.