HR Ticket Schema
Felder
HR Ticket Schema
Internal HR-only ticket. Any employee can create one; only HR (Personalabteilung) can edit/process.
hrTicketNumber
Auto-generated HR ticket number (e.g. HR-2026-00042). Set by entity.service.
title
Short subject line of the HR ticket
description
Detailed description (plain text)
descriptionHtml
Rich-text HTML version of the description (sanitized server-side)
category
HR category — drives routing/filtering inside HR
equipmentpayrollpersonalitonboardingoffboardingtrainingfeedbackotherstatus
Workflow status. Only HR can transition.
OPENIN_PROGRESSWAITINGRESOLVEDCLOSEDpriority
Priority chosen by requester; HR may re-prioritize
LOWNORMALHIGHCRITICALrequesterId
User UUID of the employee who raised the ticket. Auto-set on create.
assignedToId
HR processor user UUID (assignee).
orgUnitId
Org unit of the requester at time of creation (denormalized).
contactUserId
Optional additional contact person (user UUID) HR should coordinate with — e.g. line manager of the requester, mentor during onboarding. Distinct from requester/assignee/affected.
dueAt
Due date for the HR ticket in ISO format
estimatedMinutes
Estimated work time in minutes
affectedEmployeeIds
Additional employees (user IDs) affected by this HR ticket beyond the requester — e.g. payroll issue affecting a team, onboarding for a group. The requester is intentionally NOT auto-added since HR may file tickets on behalf of others.
confidential
Marks the ticket as sensitive (e.g. complaints, art-9 topics). UI may hide previews accordingly.
attachmentFileIds
References to uploaded files via the DMS / file service
tags
Free-form tags for filtering
statusChangedAt
Timestamp of last status change (denormalized)
resolvedAt
When status moved to RESOLVED
closedAt
When status moved to CLOSED
resolution
DEPRECATED — kept for legacy data. New HR notes / resolutions are written as comments or internal notes via the EntityActivityCard. Existing values stay in the document and remain visible through the History dialog, but no UI surfaces this field for editing anymore.
Keine Felder passen zum Filter.
Standard-Endpoints
Diese Resource folgt dem generischen CRUD-Vertrag der Plattform. Lesen Sie die Konventionen für Pagination, Idempotenz, Optimistic Locking und Audit. Die wichtigsten Endpoints:
GET /api/v1/hr_tickets— Liste, paginiert + filterbarGET /api/v1/hr_tickets/<id>— Einzelne EntityPOST /api/v1/hr_tickets— AnlegenPATCH /api/v1/hr_tickets/<id>— Teil-UpdateDELETE /api/v1/hr_tickets/<id>— Soft-DeleteGET /api/v1/hr_tickets/<id>/timeline— Audit + Aktivitäten