Unit Test Protocol (Prime TicketReceiver)
Unit Test Protocol (Prime TicketReceiver)
Actionable acceptance checks for Prime TicketReceiver on a tenant. Run after Prime Ticket is configured and at least one field user exists. Cross-ref: UAT processes.
Access
Ticket Receiver menu visible for a field-technician role
/TicketReceiver loads the responsive ticket centerField-user login redirect lands on Ticket Receiver (if configured)
Ticket workflow
Assigned New ticket appears in the New state tab
Accept moves ticket to In Progress; creator receives notification
Decline removes assignee; ticket returns to New for others
Pause on in-progress ticket; appears under paused filter
Resume from Paused returns to In Progress
Close sets Closed; supervisor notification sent; ticket visible in closed history (last week)
Detail & navigation
Ticket detail shows address, priority, due date, ticketable summary
Google Maps link opens with correct coordinates when lat/lng exist
Comment can be added and appears on refresh
Refresh & notifications
Auto-refresh toggle persists; ticket list updates within pull interval
Browser notification permission prompt shown on first visit (HTTPS)
New-ticket assignment triggers a notification when permitted
Scoring (Prime Ticket create form)
Creating a ticket against a geolocated ticketable shows ranked assignees with score in parentheses
Top-scoring technician is preselected
Ticketsystem config weights (distance / modem count / open tickets) affect ranking as expected
Sign-off
Field tech and dispatch accept Receiver + Workforce split (Receiver = my queue; Workforce = fleet map)
Failures logged with ticket id, user id, and timestamp
Parent hub: Prime TicketReceiver