Skip to content

Mobile navigation and ticket UX

The dashboard uses the existing P3MD navy/gold identity. At widths up to 768px it replaces the horizontal sidebar with a sticky compact header, a native modal menu drawer containing all management pages and account actions, and fixed shortcuts for Beranda, Tiket, Percakapan, and Lainnya. The drawer supports keyboard focus, Escape dismissal, outside dismissal, current-page indication, and scrolling for short screens. Bottom controls account for device safe-area insets; notification toasts sit above them.

Phones default to Daftar, a ticket list with requester, owner, category, priority, target, status, and next-action controls. Desktop defaults to Tabel. Kanban remains available at both sizes; on touch screens each lane scrolls horizontally and status changes remain possible with the native select instead of dragging. Explicit view choices persist during the current page session. The ticket status shortcuts complement the desktop dropdown; redundant status dropdown space is removed on phones. Advanced filters and refresh/reset utilities are collapsible.

Status Color Meaning shown in the guide
Terbuka Amber Newly received or not yet being handled
Ditangani Blue Under investigation/follow-up
Selesai Green Handling complete; can still be reviewed
Ditutup Purple Case ended and inactive

Color is supplemented by names and icons. The same mapping is applied to table/list pills, board lanes/cards, ticket detail/draft preview, and the overview status chart. Due-date warnings and priority labels remain separate from status. The guide describes the operating convention; status labels do not prove delivery, acceptance, or user confirmation.

Quick actions advance open → in progress → resolved → closed, or reopen a closed ticket. They use the existing authenticated, CSRF-protected, optimistic-version API. Pending actions disable that ticket’s controls; stale updates refresh and show the existing error instead of silently overwriting another admin. No automatic assignment or notification has been introduced.

Selection is retained when refreshing the same visible result set; tickets removed by a filter are removed from the selection. Bulk edits remain limited to 50 and use existing atomic version checks. On phones the selected-ticket controls are available above the bottom navigation, with collapsible bulk fields. A successful bulk update clears selection. Opening a ticket shows current status and a preview of an unsaved status choice; cancelling leaves the stored ticket unchanged. Activity and internal notes can be expanded within the editor.

Motion is limited to menu entry, switching list/table/board, button feedback, and a short update highlight. Reduced-motion preferences disable movement/update animations. No new frontend library, external font, CDN, backend schema, AI call, or WhatsApp send is required.

scripts/check_mobile_ticket_ux.py exercises all-page mobile navigation, list/table/board, four distinct status colors, quick actions, cancellation, two-ticket bulk changes, advanced filters, 360/390/768/1440px widths, Escape, and reduced motion against a disposable database. It asserts the database is named test. scripts/check_mobile_ticket_live.py checks the public HTTPS UI without saving tickets or changing business data. Synthetic fixtures never enter production.

Only the dashboard service needs recreation for this update. Source rollback: /opt/dirman-assist/code-backups/before-mobile-tickets/app; a protected database backup was also taken. Restore that static source and rebuild/recreate the dashboard to revert. API, WhatsApp worker, PDF worker, WAHA, PostgreSQL, and shared proxies do not need a restart.