feat(consistency): ticket-detail Delete + assets bulk-delete (MAPPS-313) #341
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!341
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/MAPPS-313-delete-affordances"
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?
QA pass flagged two outliers in the delete-affordance audit:
Brings both surfaces in line with Companies / Contracts / Projects
detail (per-row delete + confirmation) and Tickets list (bulk +
confirmation - see MAPPS-310).
Ticket detail-page Delete:
TicketDetailPage's PageHeaderactions, next to "Add Note" / "Log Time".
ConfirmDialogtitled with the ticket number + title.Spells out the cascading-delete contract (notes / attachments /
time entries).
DELETE /api/v1/tickets/{id}, toasts success, andnavigator.push(Route::TicketList)so a now-404 ticket id can'ttrap the user.
losing their place when the server rejects.
Assets list bulk-delete:
BulkActionsBar, alongside "Bulk edit".uses (MAPPS-310).
DELETE /api/v1/assets/{id}calls with the same partial-success toast copy as Tickets.
#MAPPS-313
QA pass flagged two outliers in the delete-affordance audit: - Ticket detail page had no Delete button (only the list bulk action). - Assets list had bulk-edit but no bulk-delete. Brings both surfaces in line with Companies / Contracts / Projects detail (per-row delete + confirmation) and Tickets list (bulk + confirmation - see MAPPS-310). Ticket detail-page Delete: - Adds a Danger Delete Button to `TicketDetailPage`'s PageHeader actions, next to "Add Note" / "Log Time". - Opens `ConfirmDialog` titled with the ticket number + title. Spells out the cascading-delete contract (notes / attachments / time entries). - Confirm fires `DELETE /api/v1/tickets/{id}`, toasts success, and `navigator.push(Route::TicketList)` so a now-404 ticket id can't trap the user. - Inline-error in the dialog message lets the user retry without losing their place when the server rejects. Assets list bulk-delete: - Adds a Danger "Delete selected" Button to the existing `BulkActionsBar`, alongside "Bulk edit". - Same snapshot-at-click + ConfirmDialog pattern Tickets bulk-delete uses (MAPPS-310). - Fan-out `DELETE /api/v1/assets/{id}` calls with the same partial- success toast copy as Tickets. #MAPPS-313