SingleJobsBar) is already used on the Agreements Not Signed list when the client marks the inspection with a synthetic eventEarly flag.attik-frontend/src/components/task-check/UnconfirmedOrders.tsx loads unconfirmed inspections via GET inspection with status: 'unconfirmed' and renders SingleJobsBar without passing eventBadge, so the Early Event chip never appears on that list.attik-frontend/src/components/task-check/AgreementsNeeded.tsx already implements client-side detection for a related workflow: it finds jobs with events in a near-term window and unsigned agreements, maps those rows with eventEarly: true, and passes eventBadge={inspection.eventEarly} into SingleJobsBar. That pattern is the closest in-repo reference for how the chip is triggered (the flag is not a backend field in this codebase—eventEarly only appears in that component).attik-frontend/src/components/task-check/SingleJobsBar.tsx renders the "Early Event" Chip when eventBadge is true; the row is shared across multiple worklists under attik-frontend/src/app/tools/work/[[...type]]/page.tsx (including the unconfirmed route).attik-frontend/src/components/task-check/UnconfirmedOrders.tsx is the primary surface: after fetching InspectionFullyPopulated[], derive whether each inspection qualifies as "early event" (see decisions below) and pass eventBadge into SingleJobsBar the same way AgreementsNeeded.tsx does.AgreementsNeeded.tsx only if product confirms the same definition of "early" (that list currently keys off event dates relative to a rolling beforeDate window and unsigned agreement, which is not identical to "event before inspection datetime").SingleJobsBar.tsx already supports eventBadge; no change strictly required there unless copy, styling, or tooltip should differ between worklists (decision needed).attik-frontend/src/app/tools/work/[[...type]]/page.tsx mounts UnconfirmedOrders when the route segment is unconfirmed (alongside other task-check lists).eventEarly field exists on inspection documents in attik-backend (grep shows no server usage); today's chip path is client-derived. Moving detection server-side (e.g. on GET inspection aggregation) is optional and only in scope if product wants one source of truth or to reduce payload logic (decision needed).attik-backend/src/routes/inspection.ts (or the inspection list query path used by the frontend inspection list call) would be the natural place to document and implement—not assumed for this story unless explicitly expanded.event.datetime before inspection.datetime, vs. parity with AgreementsNeeded's calendar window logic, vs. another company rule (the issue text emphasizes before inspection date).attik-frontend/src/components/task-check/UnconfirmedOrders.tsxattik-frontend/src/components/task-check/AgreementsNeeded.tsxattik-frontend/src/components/task-check/SingleJobsBar.tsxattik-frontend/src/app/tools/work/[[...type]]/page.tsxPlease authenticate to join the conversation.
Next Up
Main App
About 2 months ago
Linear
Get notified by email when there are changes.
Next Up
Main App
About 2 months ago
Linear
Get notified by email when there are changes.