Zephyr: Create Test Cycle
zephyr_create_test_cycleCreate a test cycle in Zephyr for a Jira project, defining name, schedule, status, owner, and custom fields to manage test execution.
Instructions
Create a new Test Cycle in Zephyr specified project
Toolset: Test Cycles
Parameters:
projectKey (string) required: Jira project key.
name (string) required
description (string): Description outlining the scope.
plannedStartDate (string): Planned start date of the test cycle. Format: yyyy-MM-dd'T'HH:mm:ss'Z'
plannedEndDate (string): The planned end date of the test cycle. Format: yyyy-MM-dd'T'HH:mm:ss'Z'
jiraProjectVersion (number): Jira Project Version ID. Relates to 'Version' or 'Releases' in Jira projects.
statusName (string): The status name.
folderId (number): ID of a folder to place the entity within.
ownerId (string): Atlassian Account ID of the Jira user.
customFields (record<string, any>): Multi-line text fields support HTML and should denote new lines with the <br> tag. Dates should be in the format 'yyyy-MM-dd'. Users should have values of Jira User Account IDs.
Examples:
Create a Test Cycle in project SA to ensure that the axial pump can be enabled
{
"projectKey": "SA",
"name": "Check axial pump",
"description": "Ensure the axial pump can be enabled"
}Expected Output: The newly created Test Cycle with its details and key
Create a Test Cycle to ensure that the axial pump can be enabled. The test cycle should be in project MM2, have status 'In Progress', and be planned from 2026-03-01 to 2026-03-10
{
"projectKey": "MM2",
"name": "Check axial pump",
"description": "Ensure the axial pump can be enabled",
"statusName": "In Progress",
"plannedStartDate": "2026-03-01T00:00:00Z",
"plannedEndDate": "2026-03-10T00:00:00Z"
}Expected Output: The newly created Test Cycle with its details and key
Create a Test Cycle for verifying strength of the axial pump with custom field 'Axial pump strength' having value '5' in project SA
{
"projectKey": "SA",
"name": "Check axial pump strength",
"description": "Make sure the axial pump operates at the required strength",
"customFields": {
"Axial pump strength": 5
}
}Expected Output: The newly created Test Cycle with its details and key
Create a Test Cycle in project MM2 to verify the performance of the axial pump with Jira Project Version ID 10001, owner Atlassian Account ID '12', in folder with ID 18
{
"projectKey": "MM2",
"name": "Check axial pump performance",
"description": "Ensure the axial pump performs within acceptable limits",
"jiraProjectVersion": 10001,
"ownerId": "12",
"folderId": 18
}Expected Output: The newly created Test Cycle with its details and key
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | ||
| ownerId | No | Atlassian Account ID of the Jira user. | |
| folderId | No | ID of a folder to place the entity within. | |
| projectKey | Yes | Jira project key. | |
| statusName | No | The status name. | |
| description | No | Description outlining the scope. | |
| customFields | No | Multi-line text fields support HTML and should denote new lines with the \<br\> tag. Dates should be in the format 'yyyy-MM-dd'. Users should have values of Jira User Account IDs. | |
| plannedEndDate | No | The planned end date of the test cycle. Format: yyyy-MM-dd'T'HH:mm:ss'Z' | |
| plannedStartDate | No | Planned start date of the test cycle. Format: yyyy-MM-dd'T'HH:mm:ss'Z' | |
| jiraProjectVersion | No | Jira Project Version ID. Relates to 'Version' or 'Releases' in Jira projects. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | No | The ID of the entity | |
| key | No | ||
| self | No |