feat(tickets): sortable list columns (MAPPS-289) #306
No reviewers
Labels
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
psa-systems/mokosh-apps!306
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/MAPPS-289-sortable-list-columns"
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?
The Tickets list headers were marked
sortable: truebut never wired to anonsorthandler, so clicking the column showed a pointer cursor but did nothing. Mirror theContactSortKeypattern from contacts.rs: aTicketSortKeyenum tracks the active column (Ticket / Company / Status / Priority / Assigned / Updated), aSignal<Option<(key, SortDirection)>>holds direction with toggle-cycling logic, and the filtered set is sorted client-side over the already-filtered rows. The default sort matches the existing?sort=-updated_atserver query so the first paint is unchanged; clicking a header re-orders without an extra round trip. The other list pages (Companies, Contacts) already had functional sort; the Tickets list closes the gap. Remaining lists (Projects, Assets, Contracts, Invoices) follow the same pattern and are tracked as a follow-up under this ticket - this PR captures the highest-traffic surface (the QA report specifically called out the ticket queue).#MAPPS-289