Display inspector information in worklist details
Objective
- In task-check worklists, when a user expands worklist row details for inspection-type and event-type worklists, show assigned inspector contact information (at minimum the same fields staff expect on a workorder: name plus phone and email where available), so schedulers and CSRs can reach the inspector without opening the full workorder.
- Make sure inspector assigned to event also displays in the worklist item details when the inspection in question has an event associated with it.
Background
- Worklist details should show the inspector's contact information for inspection and event-related worklists (product expectation from internal request).
- Screenshot (current vs desired context — retained from original ticket):
- Today's behavior (code): Expanded details for both flows use
PeopleBoxwithinspection.people(job contacts / roles), not a dedicated inspector block. The collapsed event row subtitle appendsinspector.nameonly when present (SingleEventBar). Inspection rows do not surface inspector identity in the bar.
Scope
Frontend — worklist UI
attik-frontend/src/components/task-check/WorklistResolver.tsx— Resolvesworklist/:id/dataand rendersSingleJobsBar+SingleJobsDropdownforinspections, andSingleEventBar+SingleEventDropdownforevents(plus grouped variants).attik-frontend/src/components/task-check/SingleJobsBar.tsx/SingleJobsDropdown.tsx— Inspection row title is datetime, address, badges, and workorder link; the dropdown showsPaymentNotes,PeopleBox(inspection.people), andActivityFeed— no inspector phone/email block today.attik-frontend/src/components/task-check/SingleEventBar.tsx— Usesevent.inspectoronly forinspector.namein the subtitle line;SingleEventDropdownagain usesPeopleBoxon the linkedinspectionandRelatedEventsSection, not the event'sinspectordocument for contact details.attik-frontend/src/components/ui/PeopleBox.tsx— Renders people on the job (contacts by role); this is not the same as employee / inspector records on_inspectorId.
Backend — worklist data
attik-backend/src/routes/worklist.ts—GET /worklist/:id/databuilds pipelines viabuildWorklistPopulationStages. Forevents, after loading the linked inspection, the pipeline$lookupinspectorsand projectsname,firstName,lastName,email,phone,image,thumbontoinspector(so email/phone can already exist on the payload for event rows). Forinspections,getInspectionPopulationPipelineis invoked withincludeInspectors: falseeverywhere in this builder, so assigned inspectors are not populated on inspection worklist rows today.
Decision needed
- Whether inspector details should mirror workorder header behavior (multiple inspectors, requested vs assigned), primary inspector only, or event row inspector only for events; and whether mobile worklists (if any) stay out of scope.
References
- Slack thread attachment on the issue (context): same Linear attachment "Message from ryan" as on the ticket.
- Worklist API:
attik-backend/src/routes/worklist.ts(GET /:id/data,buildWorklistPopulationStages). - Types:
attik-frontend/src/util/types/serverTypeCollection/worklist.ts(EventWorklistResultdocumentsinspector?: Inspector | null).
Status: Completed
Log in to comment and vote
No comments yet
Be the first to share your thoughts.