Create a new 'TestCaseFolder' entity
POST/testcase-folder
Creates a new 'TestCaseFolder' entity. Returns full entity with new id and (optional) creation metadata.
Request
- application/json
Body
required
The unique entity id - must be a positive integer
A descriptive title for this entity or mapping (1 to 200 characters)
An integer sort index for natural ordering of this entity or mapping value - value must be in range (-999999999999999,999999999999999)
If the entity has been soft-deleted this value is true
The creation time for this entity or mapping value
The creator user id of this entity or mapping value - or zero if created by the system
The last modification time for this entity or mapping value
The id of the user who last modified or undeleted this entity or mapping value - or zero if modified by the system
The soft-deletion time for this entity or mapping value
The id of the user who deleted this entity or mapping value - or zero if deleted by the system
A tag for detecting conflicting modifications - current value (may be empty) must be passed along in an update (or update must be forced)
The project id this entity or mapping belongs to
The id of the folder's parent in the tree structure (no cycles allowed)
An optional description for this test case folder (can be a rich text document)
Responses
- 200
- 4XX
- 5XX
Returns a single TestCaseFolder
- application/json
- Schema
- Example (from schema)
Schema
The unique entity id - must be a positive integer
A descriptive title for this entity or mapping (1 to 200 characters)
An integer sort index for natural ordering of this entity or mapping value - value must be in range (-999999999999999,999999999999999)
If the entity has been soft-deleted this value is true
The creation time for this entity or mapping value
The creator user id of this entity or mapping value - or zero if created by the system
The last modification time for this entity or mapping value
The id of the user who last modified or undeleted this entity or mapping value - or zero if modified by the system
The soft-deletion time for this entity or mapping value
The id of the user who deleted this entity or mapping value - or zero if deleted by the system
A tag for detecting conflicting modifications - current value (may be empty) must be passed along in an update (or update must be forced)
The project id this entity or mapping belongs to
The id of the folder's parent in the tree structure (no cycles allowed)
An optional description for this test case folder (can be a rich text document)
{
"id": 0,
"title": "A Descriptive Title",
"sort_index": 0,
"is_deleted": true,
"created_at": "1970-01-01T00:00:00.000Z",
"created_by": 0,
"modified_at": "1970-01-01T00:00:00.000Z",
"modified_by": 0,
"deleted_at": "1970-01-01T00:00:00.000Z",
"deleted_by": 0,
"_etag": "string",
"project_id": 0,
"testcase_folder_parent_id": 0,
"description": "string"
}
The request failed because invalid request parameters or data were supplied or access was denied.
- application/json
- Schema
- Example (from schema)
Schema
The error code describing the general error category.
The HTTP status code.
The actual error message describing the error in more detail.
The request id for following up on specific errors.
{
"code": "API_INVALID_INPUT_DATA",
"status": 0,
"message": "string",
"reqid": "string"
}
The request failed because an error occurred during processing of the request.
- application/json
- Schema
- Example (from schema)
Schema
The error code describing the general error category.
The HTTP status code.
The actual error message describing the error in more detail.
The request id for following up on specific errors.
{
"code": "API_INVALID_INPUT_DATA",
"status": 0,
"message": "string",
"reqid": "string"
}