feat(tickets,assets): bidirectional asset/ticket link (PMS-344) #190

Merged
YousifShkara merged 1 commit from feat/pms-344-asset-picker-and-related-tickets into main 2026-06-16 09:06:14 +02:00
Owner

Tickets can now be associated with assets and the link is surfaced from both sides. The New Ticket form mounts a reusable AssetPicker beside the Priority Select so the technician can attach the asset when filing. The ticket detail sidebar gains an inline editor that fires PUT /tickets/{id} with asset_id, matching the inline status/priority/assignee editors from PMS-359; clearing the picker sends null so the server unsets the association. The asset detail page gains a "Related Tickets" card that fetches GET /tickets?asset_id=, rendering each ticket as a click-through link with its number, title, status and priority. The reusable AssetPicker mirrors CompanyPicker (search + click-to-select dropdown, selected-chip state with Change button) and intentionally omits an inline-create affordance, since asset creation is heavier than company creation and is better done from the Assets page proper.

#PMS-344

Tickets can now be associated with assets and the link is surfaced from both sides. The New Ticket form mounts a reusable AssetPicker beside the Priority Select so the technician can attach the asset when filing. The ticket detail sidebar gains an inline editor that fires PUT /tickets/{id} with `asset_id`, matching the inline status/priority/assignee editors from PMS-359; clearing the picker sends null so the server unsets the association. The asset detail page gains a "Related Tickets" card that fetches GET /tickets?asset_id=<id>, rendering each ticket as a click-through link with its number, title, status and priority. The reusable AssetPicker mirrors CompanyPicker (search + click-to-select dropdown, selected-chip state with Change button) and intentionally omits an inline-create affordance, since asset creation is heavier than company creation and is better done from the Assets page proper. #PMS-344
feat(tickets,assets): bidirectional asset/ticket link (PMS-344)
All checks were successful
Create release / Create release from merged PR (pull_request) Has been skipped
Check / clippy + fmt + tests (pull_request) Successful in 59s
b8cf377131
Tickets can now be associated with assets and the link is surfaced from both sides. The New Ticket form mounts a reusable AssetPicker beside the Priority Select so the technician can attach the asset when filing. The ticket detail sidebar gains an inline editor that fires PUT /tickets/{id} with `asset_id`, matching the inline status/priority/assignee editors from PMS-359; clearing the picker sends null so the server unsets the association. The asset detail page gains a "Related Tickets" card that fetches GET /tickets?asset_id=<id>, rendering each ticket as a click-through link with its number, title, status and priority. The reusable AssetPicker mirrors CompanyPicker (search + click-to-select dropdown, selected-chip state with Change button) and intentionally omits an inline-create affordance, since asset creation is heavier than company creation and is better done from the Assets page proper.

#PMS-344
YousifShkara deleted branch feat/pms-344-asset-picker-and-related-tickets 2026-06-16 09:06:14 +02:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
psa-systems/mokosh-apps!190
No description provided.