Show required-info as distinct worklist columns with blank visibility
Objective
- Let teams add selected required-info fields as separate, scannable columns on custom worklists (and any surface that reuses the same column model) so operators can see what is filled in and what is still missing without expanding each row or opening the workorder/quote.
- Replace the limitation of the current stacked Required Info group column, which only surfaces populated values and collapses multiple fields into one cell — insufficient for operational queues that need spreadsheet-style triage.
- Support blank-state visibility in every required-info column (empty/missing values must remain visible in the grid, not hidden), so teams can work down a process checklist from the list view.
Background
- ATT-1639 (Done) shipped a worklist column catalog, saved
visibleColumnsonworklistSchema, and row rendering viaSingleJobsBar,SingleQuoteBar, andSingleEventBarinWorklistResolver.tsx. - ATT-1614 (Done) added required-info to the expanded row panel via
WorklistRequiredInfoPanel.tsx— useful for detail, but not the at-a-glance column scan users asked for on the June 16 implementation call. - Today’s group column (
grp_risentinel) renders throughGroupInfoCell.tsx, which skips fields with no value (if (!val) return null) and stacks remaining values vertically in a single ~200px column. Row bars pass all company required-info definitions into that cell today, not the worklist’sriGroupFieldsselection. - The column picker in
NewWorklistDrawer.tsxonly exposesgrp_rias one toggle (“Display all required info fields in a single column”) with no sub-field picker (unlikegrp_cr, which lets users choose contact roles). Individualri_<fieldId>keys are stripped from the picker even though row renderers already support them. - Individual
ri_*column rendering already exists inSingleJobsBar.tsx,SingleQuoteBar.tsx, andSingleEventBar.tsx: each shows the field value or an em-dash (—) when blank. Headers resolve field names viagetColumnHeaders()incolumnConfig.ts. The product gap is picker + persistence + blank-state UX policy, not greenfield row rendering. - Worklist data payloads already include
requiredInfoValueson inspections and quotes viabuildWorklistPopulationStagesinattik-backend/src/routes/worklist.ts. Required-info definitions come fromGET required-info(requiredInfoSchema.ts). - “Custom fields” in stakeholder language maps to Attik required-info definitions (including Spectora-synced fields via
_spectoraCustomFieldId), not a separate field system. Static quote columns likereason_not_bookedandfollow_up_datealready live in the static catalog incolumnConfig.tsand are out of this issue’s core ask unless product expands scope. - On the June 16 implementation call, users said the stacked required-info summary is not enough — they want chosen fields as distinct columns with blank values visible so the worklist works like a process spreadsheet.
- No attachments, linked documents, or inline media on this ticket.
Product Decisions
Locked
- Distinct columns, not stacked-only — Selected required-info fields must appear as separate grid columns with their own headers, not only inside the single stacked
grp_ricell. - Blank-state visibility — Empty/missing values for a selected field must remain visible in the column (not omitted from the row), so operators can see gaps without opening the record.
- Read-only scan (v1 assumption) — Primary outcome is visibility/triage from the list row; inline editing from the column is not assumed unless product expands scope.
- Required-info fields only — Scope centers on company required-info definitions (
required-infoAPI /requiredInfoValueson rows), not arbitrary Mongo paths or Reports HubrequiredInfoValue.*export columns (though the same field IDs may apply).
Open
- Relationship to
grp_ri— Replace the stacked group column with per-fieldri_*columns, keep both (group for quick summary + individual columns for triage), or upgradegrp_rito show selected fields with blanks instead of adding individual columns? - Field picker UX — Add required-info fields to the column picker in
NewWorklistDrawer.tsxas individual toggles (like contact roles undergrp_cr), a nested multi-select undergrp_ri, or a separate “Add required-info column” flow? - Which fields are selectable — All non-hidden company required-info definitions, or only fields applicable to the row’s services (respecting
_requiredInfoIdon services)? If a field does not apply to a row, should the column show blank, “N/A”, or hide for that row? - Blank-state presentation — Is em-dash (
—) sufficient, or should blanks use stronger affordances (e.g. “Missing”, muted label, color/icon for required-but-empty fields)? - Entity and surface scope — Custom worklists only for v1, or also default prebuilt worklists (ATT-1937)? Apply to inspections + quotes + events, or a subset?
- Column limit / performance — Any cap on how many required-info columns one worklist may enable before horizontal scroll becomes unusable?
- Hidden required-info fields — Should fields marked
hidden: trueon the definition be excluded from the picker entirely? - Value formatting — Should column cells reuse workorder formatting (dates, booleans, select labels) from
WorklistRequiredInfoPanel.tsx/RequiredInfoAccordion, or plain string truncation is enough for v1?
Scope
Frontend (attik-frontend)
- Column picker —
NewWorklistDrawer.tsxcolumn section currently blocks individualri_*keys and offersgrp_riwithout sub-field selection; extend so teams can add specific required-info fields as columns invisibleColumns(and persist order via drag-and-drop). - Row rendering —
SingleJobsBar.tsx,SingleQuoteBar.tsx,SingleEventBar.tsxalready render individualri_*keys with blank em-dashes; align blank-state UX with product decision and ensure selected fields drive headers viaWorklistTableHeader.tsx/getColumnHeaders(). - Group column —
GroupInfoCell.tsxandgrp_rihandling in row bars may need updates if product retires or upgrades the stacked column (today hides blanks and ignoresriGroupFields). - Migration —
WorklistResolver.tsxmigrateWorklistColumns()converts legacy individualri_*keys togrp_ri; revisit if individual columns become the preferred model again. - Catalog / layout —
columnConfig.tsassigns ~120px width to extra keys and supports dynamic headers fromrequiredInfoFields; may need width or formatting tweaks for many RI columns.
Backend (attik-backend)
worklistSchema.tsalready storesvisibleColumns,riGroupFields, andcrGroupFields; individualri_<id>keys invisibleColumnsmay be sufficient for persistence without schema changes — confirm whetherriGroupFieldsremains needed ifgrp_riis deprecated or upgraded.worklist.tsdata pipeline already populatesrequiredInfoValuesfor worklist rows; confirm event worklists resolve inspection-linked values correctly for event-type lists.- No new API strictly required if picker writes
ri_*keys into existingvisibleColumnsPATCH — unless product wants server-side validation of field IDs.
Out of scope (unless product expands Open decisions)
- Inline editing of required-info from the worklist row/column.
- Static catalog columns (
reason_not_booked,follow_up_date, etc.) — already shipped separately in ATT-1639 catalog. - ATT-1937 default prebuilt worklist column config — adjacent; may consume this issue’s column model once built.
- Reports Hub / data-export
requiredInfoValue.<id>column namespace — different surface; reuse field IDs only.
References
- ATT-1639 — Custom worklist column catalog (Done)
- ATT-1614 — Required-info in expanded row (Done)
- ATT-1937 — Default worklist column config (Backlog, adjacent)
- Frontend:
attik-frontend/src/util/worklist/columnConfig.ts,attik-frontend/src/components/task-check/GroupInfoCell.tsx,attik-frontend/src/app/tools/work/NewWorklistDrawer.tsx - Backend:
attik-backend/src/models/worklistSchema.ts,attik-backend/src/routes/worklist.ts
Status: Planned
Log in to comment and vote
No comments yet
Be the first to share your thoughts.