Map Tracker Items to a Working-Set
Since Codebeamer release 2.0 (HUSKY), a new endpoint is available in Swagger to add trackers items to a working-set:
POST/v3/working-sets/items-mapping
Usage
To map a tracker to a working-set,
- Use the POST/v3/working-sets/items-mapping endpoint in Swagger.
- Add the relevant details to the Request body and click Execute.
Example:
{
"items": [
{
"id": 106274,
"name": "tc1d",
"type": "Testcase",
"referenceData": {
"suspectPropagation": "DO_NOT_PROPAGATE"
},
"testStepReuse": true
}
],
"targetWorkingSet": {
"id": 668563,
"name": "ws1",
"type": "WorkingSetReference"
}
}
The following details need to be provided in the Request body:
Property |
Description |
"items" |
"id" |
The ID of the tracker item to be mapped to the working-set. |
"name" |
The name of the tracker item to be mapped to the working-set. |
"type" |
The type of the tracker item to be mapped to the working-set. |
"referenceData": {
"suspectPropagation" |
The suspect propagation setting of the tracker item. |
"testStepReuse" |
Test step reuse is enabled (true) or disabled (false). |
"targetWorkingSet" |
"id" |
The ID of the working-set to which the tracker item is mapped. |
"name" |
The name of the target working-set to which the tracker item is mapped. |
"type" |
The type of the target working-set to which the tracker item is mapped. |
In the Server response section, Code 200 is displayed, that is, the API call has been executed successfully.