Update Subtask

This endpoint allows you to update an existing subtask. All fields are optional; only the submitted fields will be updated.

Request

curl --request PATCH \
     --url 'https://www.zep-online.de/zepinstanz/next/api/v1/tickets/123/subtasks/456' \
     --header 'Accept: application/json' \
     --header 'Authorization: Bearer {token}' \
     --header 'Content-Type: application/json' \
     --data '{
  "status": 2,
  "processor_username": "jane.smith",
  "deadline": "2024-11-28",
  "planned_hours": 15.0
}'

Parameters

• id (integer, required): The ID of the parent ticket
• subtask_id (integer, required): The ID of the subtask to update

Optional Fields

All fields are optional. You can update individual or multiple fields at once:

• subject (string): Subject of the subtask (max. 255 characters)
• name (string): Name/title of the subtask (max. 255 characters)
• status (integer): Subtask status (1=New, 2=In Process, 3=Done, 4=Rejected, 5=Approved, 8=Billed)
• creator_username (string): Username of the creator
• customer_reference (string): Customer reference number (max. 255 characters)
• start_date (string): Start date (YYYY-MM-DD)
• receipt_date (string): Receipt date (YYYY-MM-DD)
• deadline (string): Due date (YYYY-MM-DD)
• planned_hours (number): Planned hours
• prevent_overbooking (integer): Overbooking prevention (0-4)
• processor_username (string): Processor username
• keywords (string): Keywords (max. 255 characters)
• customer_contact_person (string): Customer contact email
• categories (array): Category names

Response

{
	"data": {
		"id": 456,
		"ticket_id": 123,
		"subject": "Perform database optimization",
		"name": "DB Optimization Phase 1",
		"status": 2,
		"creator_username": "john.doe",
		"processor_username": "jane.smith",
		"start_date": "2024-11-20",
		"deadline": "2024-11-28",
		"planned_hours": "15.00",
		"created": "2024-11-18T14:30:00.000000Z",
		"modified": "2024-11-19T10:15:00.000000Z",
		"categories": [
			{
				"id": 22,
				"name": "Performance"
			},
			{
				"id": 18,
				"name": "Backend"
			}
		]
	}
}

Error Codes

• 401 Unauthorized: Invalid or missing authentication
• 404 Not Found: Ticket or subtask not found
• 422 Unprocessable Entity: Validation error