Reference & Data Model
Overview of time tracking data
Time tracking works in two stages: a running or stopped timer measures time; a time log with its time entries assigns it to a project and task and goes through approval.
What defines this data type
Section titled “What defines this data type”The central entity is the Time log (time_log): exactly one per employee, day, project and optional task. It carries the status, billability and description. The hours themselves live in its Time entries (time_entry), each a from–to time span. A Timer (timer) is a measured time span that has not been assigned yet; the Active timer (active_timer) is the draft that is currently ticking.
Time tracking data is business data: anyone whose grant at the project allows it may see, edit or approve time logs (see Access: who may do what). Only the active timer is private per user.
Entities and relations
Section titled “Entities and relations”User (ch. 1) ──1:1──► Active timer (active_timer) [private, server only] │ stop ▼ Timer (timer) ── „Neuen Zeiteintrag aus Timer erstellen“ / „Zu vorhandener Zeiterfassung hinzufügen“ ──┐ ▼Employee (ch. 2) ──► Time log (time_log) ◄── Project (ch. 3) ◄── Task (ch. 3, optional) │ has many ▼ Time entry (time_entry) start_time … end_timeLifecycle: Timer → Time log → Approval
Section titled “Lifecycle: Timer → Time log → Approval” [Start timer] [„Neue Zeiterfassung“] │ │ ▼ │ Active timer ──stop──► Timer ──convert─────────┤ (active_timer) (timer) │ (timer is deleted) │ ▼ │ Time log „Ausstehend“ (pending) │ + time entries (editable) │ │ discard ┌─────┴──────────┐ (delete) ▼ ▼ „Genehmigt“ „Abgelehnt“ (approved) (rejected) LOCKED ◄──────────► editable │ Status back to „Ausstehend“/„Abgelehnt“ lifts the lock ▼ Personnel costs posted (only on the FIRST approval)Entities in this chapter
Section titled “Entities in this chapter”| Entity | Purpose | Where in the app |
|---|---|---|
Active timer (active_timer) |
The timer currently ticking for a user, across all devices | Sidebar (timer chip), „Erfassungsansicht“ (Tracking view) (Guides › Time tracking) |
Timer (timer) |
Stopped time span without project reference, waiting to be assigned | „Erfassungsansicht“ › timer rows |
Time log (time_log) |
Header: employee, day, project, task, status, billable | „Erfassungsansicht“, „Detailansicht“ (Detail view), „Freigabeansicht“ (Approval view) |
Time entry (time_entry) |
From–to time span within a time log | Dialog „Zeiterfassung“ › „Zeitenbuchungen“ |
Connections to other chapters
Section titled “Connections to other chapters”- Resources (ch. 4): logged hours are the „Ist-Aufwand“ (actual effort) in the „Ressourceneinsatz“ (resource usage) of a task, see Employee usage.
- Planning (ch. 3): every time log belongs to a Project and optionally to a Task; neither can be deleted while approved time logs are attached to it.
- Finance (ch. 6, 12): approval posts a one-time cost event „Personalkosten aus Zeiterfassung“ (personnel costs from time tracking), see Actual personnel costs and Cost event.
- Locks (ch. 12): the lock on approved time logs is a server rule, see Locks.
- KPIs (ch. 13): target/total hours, tracking rate, open approvals, see Work and Counts.