Delete ticket

Soft delete entity.

Datenmodell

Diese Operation arbeitet auf der Entität Ticket (ticket). Alle 80 Felder — Typ, Validierung, Pflichtangabe, Beziehungen — stehen in der Schema-Referenz.

• Pflichtfelder: title, status, priority
• Server-verwaltet: _id, schema, schemaVersion, tenantId, version, createdAt, updatedAt, createdBy, updatedBy, deletedAt, deletedBy, ticketNumber, dispatch, aiSummary, aiSummaryAttemptedAt, budget.consumedMinutes, budget.locked, budget.lockedAt, budget.lockedReason, budget.unlockRequestId, budget.capHistory, salesOrderId, salesOrderItemId, salesOrderItemSource, standaloneBilling.enabledBy, standaloneBilling.enabledAt, standaloneBilling.performanceRecordId, standaloneBilling.performanceRecordNumber, standaloneBilling.invoicedAt, handlingTier, handedToCustomerAt, slaPausedMs, handoverPreviousAssigneeId, convertedTo, convertedFrom, aiReopenSuggestion, aiReopenDecision, aiReopenConfidence, aiReopenBasis, aiReopenConfirmedBy, externalOwnership, externalOwnershipTakenAt, externalOwnershipTakenBy, externalOwnershipTag — diese Felder vergibt die Plattform; im Request werden sie verworfen.

Pfad-Parameter

Beispiel

curl -X DELETE https://api.codemeta-os.de/v1/tickets/{id} \
  -H "X-Tenant-Id: $TENANT" \
  -b cookies.txt

const result = await cm.tickets.delete();

Antwortcodes