create_test_run
Create a new test run in Zephyr Scale by specifying project, name, and optional test cases, plan, dates, and custom fields.
Instructions
Create a new test run
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Test run name (required) | |
| owner | No | Test run owner (optional) | |
| folder | No | Folder path (optional) | |
| issue_key | No | Single Jira issue key to link to the test cycle (e.g. "PROJ-123"). On Cloud, resolved to a numeric ID via Jira REST API — requires JIRA_USERNAME + JIRA_API_TOKEN env vars. | |
| description | No | Test run description (optional) | |
| environment | No | Test environment name (optional). On Cloud, applied to each test execution (environmentName). On Data Center, set at cycle level. | |
| issue_links | No | Array of Jira issue keys to link to the test cycle (e.g. ["PROJ-123", "PROJ-456"]). On Cloud, each key is resolved to a numeric ID via Jira REST API — requires JIRA_USERNAME + JIRA_API_TOKEN env vars. Failures are reported as warnings and do not fail the tool call. | |
| project_key | Yes | Project key (required) | |
| custom_fields | No | Custom fields object (optional) | |
| test_plan_key | No | Test plan key to link this test run to (optional) | |
| test_case_keys | No | Array of test case keys to include in the test run | |
| planned_end_date | No | Planned end date in ISO format (optional) | |
| planned_start_date | No | Planned start date in ISO format (optional) | |
| jira_project_version | No | Jira project version/release ID to link this test cycle to (optional, Cloud only — use the numeric version ID). |