QTM4J: Unlink Requirements from Test Cycle
qtm4j_unlink_requirements_from_test_cycleRemove Jira requirements from a QTM4J test cycle by specifying requirement keys or unlinking all at once. Clean up links before repopulating the cycle.
Instructions
Unlink one or more Jira requirements from a QTM4J test cycle by requirement keys, or unlink all requirements at once with unLinkAll.
Toolset: Test Cycles
Parameters:
cycleKey (string) required: Test cycle key in '{PROJECT_KEY}-TR-{id}' format (e.g., 'SCRUM-TR-1'). Resolved to the internal cycle UID automatically.
requirementKeys (array): List of Jira requirement keys to unlink (e.g., ['SCRUM-1', 'SCRUM-2']). Resolved to internal IDs automatically. Provide this OR unLinkAll — not both.
unLinkAll (boolean): If true, all requirements are unlinked from the cycle. Ignores requirementKeys.
Output Description: Confirmation with the cycle key and unlinked: true. Warnings are included if any requirements could not be resolved or unlinked.
Use Cases: 1. Remove one or more Jira requirements from a test cycle by key 2. Unlink all requirements from a test cycle at once 3. Clean up requirement links before repopulating a test cycle
Examples:
Unlink two requirements by key
{
"cycleKey": "SCRUM-TR-1",
"requirementKeys": [
"SCRUM-1",
"SCRUM-2"
]
}Expected Output: Requirements SCRUM-1 and SCRUM-2 unlinked from test cycle
Unlink all requirements from a cycle
{
"cycleKey": "SCRUM-TR-1",
"unLinkAll": true
}Expected Output: All requirements unlinked from test cycle
Hints: 1. PREREQUISITE: set_project_context must be called before this tool. NEVER auto-select a project. 2. CYCLE KEY FORMAT: '{PROJECT_KEY}-TR-{id}' — e.g. 'SCRUM-TR-1'. Resolved to internal UID automatically. 3. Requirement keys follow Jira issue key format: '{PROJECT_KEY}-{number}' (e.g. 'SCRUM-1'). 4. Provide either requirementKeys or unLinkAll: true — not both. 5. unLinkAll: true removes every requirement from the cycle — no need to list them individually. 6. If a requirement key cannot be resolved or unlinked, it is reported in warnings and other requirements are still unlinked.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| cycleKey | Yes | Test cycle key in '{PROJECT_KEY}-TR-{id}' format (e.g., 'SCRUM-TR-1'). Resolved to the internal cycle UID automatically. | |
| unLinkAll | No | If true, all requirements are unlinked from the cycle. Ignores requirementKeys. | |
| requirementKeys | No | List of Jira requirement keys to unlink (e.g., ['SCRUM-1', 'SCRUM-2']). Resolved to internal IDs automatically. Provide this OR unLinkAll — not both. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| cycleKey | Yes | ||
| unlinked | Yes |