test(tickets): pin server-side inline status/priority/assignee edit + SLA recalc

David commented

2026-06-16 17:46:12 +02:00

Owner

The PMS-359 ticket-detail inline editor (status / priority / assignee dropdowns) lives in the mokosh-apps SPA, but its server contract is entirely in mokosh-server's PUT /api/v1/tickets/{id} path, which already accepts status_id / priority_id / assigned_to_id, writes audit rows, and recalculates SLA due dates when priority changes. That server behaviour had no integration coverage for the inline-edit workflow, only for title and description edits.

This adds ticket_inline_status_priority_assignee_edits_persist_audit_and_recalc_sla to tests/tickets.rs, pinning the server-side acceptance criteria end to end: each of the three field edits persists and is echoed on the re-fetched DTO; the per-record change-history feed records a distinct update entry for the status, priority, and assignee change; promoting Medium -> High shortens the SLA due date (24h -> 8h resolution targets from the seeded Standard SLA policy); and an unauthenticated PUT is rejected so the "must be logged in" gate is covered. No production code changes were needed; the functionality already existed.

#PMS-359

The PMS-359 ticket-detail inline editor (status / priority / assignee dropdowns) lives in the mokosh-apps SPA, but its server contract is entirely in mokosh-server's PUT /api/v1/tickets/{id} path, which already accepts status_id / priority_id / assigned_to_id, writes audit rows, and recalculates SLA due dates when priority changes. That server behaviour had no integration coverage for the inline-edit workflow, only for title and description edits. This adds ticket_inline_status_priority_assignee_edits_persist_audit_and_recalc_sla to tests/tickets.rs, pinning the server-side acceptance criteria end to end: each of the three field edits persists and is echoed on the re-fetched DTO; the per-record change-history feed records a distinct update entry for the status, priority, and assignee change; promoting Medium -> High shortens the SLA due date (24h -> 8h resolution targets from the seeded Standard SLA policy); and an unauthenticated PUT is rejected so the "must be logged in" gate is covered. No production code changes were needed; the functionality already existed. #PMS-359

vas2000-work force-pushed test/pms-359-ticket-inline-edits from 83bee92cb9

Create release / Create release from merged PR (pull_request) Has been skipped

Details

Check / fmt + clippy + compile + unit/doc tests (pull_request) Failing after 52s

Details

Integration / integration tests (pull_request) Failing after 1m23s

Details

E2E / Playwright against staging (pull_request) Successful in 1m12s

Details

to 25036062a2

E2E / Playwright against staging (pull_request) Successful in 1m4s

Details