create_test_results_bulk
Create multiple test results for a test run in a single API call. Each result entry must reference an existing test case key and can include status, assignee, duration, and other fields.
Instructions
Create NEW executions (test results) for several test cases of one test run in a single call. Every element's testCaseKey must already be one of the run's items — the run's item list is fixed when the run is created and this tool cannot extend it. In each element only the fields you pass are sent. Default statuses: 'Not Executed', 'In Progress', 'Pass', 'Fail', 'Blocked' — case-sensitive internal names; instances may define custom ones. Durations (executionTime) are in milliseconds; dates are ISO 8601. scriptResults record per-step outcomes as { index (0-based), status, comment? }. matchEnvironment / matchUserKey apply to the whole batch and disambiguate run items when the same test case is included in the run several times. Returns the array of created result ids.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| results | Yes | One entry per result to create; each targets an existing run item by testCaseKey | |
| testRunKey | Yes | Test run (cycle) key, e.g. PROJ-R123 | |
| matchUserKey | No | Run-item selector, sent as the 'userKey' QUERY parameter (never in the body): when the same test case is included in the run as several items, targets the item by its executor's Jira user key (e.g. 'JIRAUSER10000'). | |
| matchEnvironment | No | Run-item selector, sent as the 'environment' QUERY parameter (never in the body): when the same test case is included in the run as several items, targets the item with this environment (case-sensitive). Distinct from the 'environment' body field, which sets the environment recorded on the result. |