Add source filter to Repair Lists page (QwikFix, Thumbtack)
Objective
- Allow staff to filter the Repair Lists page by submission source (e.g. QwikFix, Thumbtack) so they can quickly identify which repair list submissions came from a specific lead channel without having to open individual records.
- Give teams a way to segment repair list activity by channel for operational and coaching purposes.
Background
- The Repair Lists page (
/inspections/repair-lists) currently supports filtering bystatusonly — surfaced viaStatusSelector.tsxand passed as a query param toGET /repair-list. There is no source or origin field on the filter UI or the underlying query. - Shayna Turilli (SW) raised this on the SW/SE call on July 6, 2026 — she specifically mentioned wanting to pull a list of contacts who came through QwikFix vs Thumbtack to understand which agents are using the service, how frequently, and where education or follow-up is needed.
- Whether repair list records currently carry a source or origin field is an open question for engineering — no
sourcefield was found in a search of the repair list route or client component. If it doesn't exist, it would need to be stored at creation time.
Product Decisions
Open
- Source field existence — Does the
SavedRepairListmodel currently store a source/origin field (e.g. QwikFix, Thumbtack, internal)? If not, how is source determined at the time a repair list is submitted — is it inferrable from a linked contact, quote, or integration record? - Filter UI — Should source be a dropdown filter on the Repair Lists page alongside the existing status filter, or a separate column/tag on each row in
SingleRepairListBar.tsx? - Scope of sources — Which sources need to be surfaced initially? At minimum: QwikFix and Thumbtack. Are there others?
Scope
Backend
apps/backend/src/routes/repairList.ts— Confirm whethersourceor origin is a filterable field onGET /repair-list; add if not present.SavedRepairListmodel — Confirm whether a source field exists and is populated at creation; if not, determine how to store it going forward.
Frontend
apps/frontend/src/app/tools/inspections/repair-lists/components/RepairListsClient.tsx— Currently passesstatusand_companyIdparams toGET /repair-list; would need asourceparam added.apps/frontend/src/app/tools/inspections/repair-lists/components/StatusSelector.tsx— Reference pattern for adding a source filter alongside the existing status filter.apps/frontend/src/app/tools/inspections/repair-lists/components/SingleRepairListBar.tsx— May need a source tag or label added to each row for visibility at a glance.
References
apps/backend/src/routes/repairList.tsapps/frontend/src/app/tools/inspections/repair-lists/components/RepairListsClient.tsxapps/frontend/src/app/tools/inspections/repair-lists/components/StatusSelector.tsxapps/frontend/src/app/tools/inspections/repair-lists/components/SingleRepairListBar.tsx- Related: ATT-1480 (Add Repair Lists to main sidebar navigation)
Status: Planned
Log in to comment and vote
No comments yet
Be the first to share your thoughts.