https://sonarly.com/issue/33893?type=bug
Dashboard widget filters use a side panel code path that delegates RELATION field filtering to FormFieldInput, which has no "Me" (current workspace member) option, unlike regular views.
Fix: Added explicit handling for `FieldMetadataType.RELATION` filter type in `AdvancedFilterSidePanelValueFormInput`, which is the value input component used by dashboard widget filters (both chart and record table widgets).
**Problem:** When users set a RELATION filter (e.g., "Account Owner") in dashboard widgets, the side panel filter component fell through to the generic `FormFieldInput` → `FormRelationToOneFieldInput` → `FormSingleRecordPicker`, which is a plain record picker with no "Me" (current workspace member) option.
**Fix:** Added a new conditional block before the `FormFieldInput` fallthrough that checks for `FieldMetadataType.RELATION` and renders `ObjectFilterDropdownSearchInput` + `ObjectFilterDropdownRecordSelect` — the same components used by the regular view filter path (`AdvancedFilterDropdownFilterInput`). `ObjectFilterDropdownRecordSelect` automatically shows the "Me" pinned item when the relation target is `workspaceMember` (line 141 of that component: `objectNameSingular === 'workspaceMember'`).
The `dropdownInstanceId` is already computed in the component (line 52-53) and the parent `AdvancedFilterSidePanelRecordFilterColumn` already provides the required `ObjectFilterDropdownComponentInstanceContext`, so no additional context setup is needed.
Three new imports were added: `ObjectFilterDropdownRecordSelect`, `ObjectFilterDropdownSearchInput`, and `DropdownMenuSeparator` — all existing components already used elsewhere in the codebase.
Sonarly Claude Code
65aa1e48b5