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 by status only — surfaced via StatusSelector.tsx and passed as a query param to GET /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 source field 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

  1. Source field existence — Does the SavedRepairList model 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?
  2. 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?
  3. 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 whether source or origin is a filterable field on GET /repair-list; add if not present.
  • SavedRepairList model — 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 passes status and _companyId params to GET /repair-list; would need a source param 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.ts
  • apps/frontend/src/app/tools/inspections/repair-lists/components/RepairListsClient.tsx
  • apps/frontend/src/app/tools/inspections/repair-lists/components/StatusSelector.tsx
  • apps/frontend/src/app/tools/inspections/repair-lists/components/SingleRepairListBar.tsx
  • Related: ATT-1480 (Add Repair Lists to main sidebar navigation)

Please authenticate to join the conversation.

Upvoters
Status

Planned

Board
🏠

Main App

Date

About 2 hours ago

Author

Linear

Subscribe to post

Get notified by email when there are changes.