style(time-tracking): rustfmt the work_category unit tests #297
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/PMS-394-time-entry-general-category"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Apply cargo fmt to the PMS-394 derive_work_category test assertions so
just check(cargo fmt --all --check) passes.#PMS-394
Make ticket association one selectable option rather than a precondition for logging time. Ticketless time is now classifiable as overhead (admin tasks, calls, reception work) instead of unattributed. Migration 054 adds a nullable work_category VARCHAR(20) DEFAULT 'ticketed' CHECK (work_category IN ('ticketed','project','general')) to time_entries and backfills existing rows from the presence of ticket_id / project_id (ticketed > project > general). Adds work_category to CreateTimeEntryRequest, UpdateTimeEntryRequest, and TimeEntryResponse in mokosh-types. The service derives the value from the work item when the client omits it (general when both ticket_id and project_id are absent) and rejects the contradiction of work_category = 'ticketed' with no ticket_id as a 400. create / update / list / get all read and write the column. company_id stays NOT NULL and required for general-bucket entries. #PMS-394