Jira Ticket: ECSCOPY-2
Priority: Medium
Components: None
Labels: priority:medium, app-ui, bug, crm-write
Description:
Customer Brentwood School (Portal ID: 2299) reports that in the Windfall App UI, spouse names are swapped between partners for some households, while the underlying export data appears correct. Some impacted example IDs shared by the customer: 2793, 2793-SP, 2050, 2001-32, 2023-740, 2020-131. (This list is not exhaustive).
Expected behavior: Spouse A's name should remain consistently associated with Spouse A across the App, matching the exported file; same for Spouse B.
Actual behavior: In the App UI, the displayed names appear cross-wired between spouses, but when exporting the same records, the CSV shows the correct, non-swapped values.
Request: Investigate how spouse/household relationships and primary/secondary contact ordering are being resolved in the App, confirm whether this is limited to Brentwood School or systemic, and fix any incorrect join or display logic so that UI surfaces the same name pairings as the export pipeline.
Triage Comments:
Triage: Prioritized as Medium — Brentwood School (2299) reports spouse names are swapped in the App UI while the export data is correct, indicating a display/join logic bug. The issue may be systemic across households but has a workaround (use the export), keeping it at Medium. Labeled bug, crm-write, app-ui.
Jira Ticket: ECSCOPY-2
Priority: Medium
Components: None
Labels: priority:medium, app-ui, bug, crm-write
Description:
Customer Brentwood School (Portal ID: 2299) reports that in the Windfall App UI, spouse names are swapped between partners for some households, while the underlying export data appears correct. Some impacted example IDs shared by the customer: 2793, 2793-SP, 2050, 2001-32, 2023-740, 2020-131. (This list is not exhaustive).
Expected behavior: Spouse A's name should remain consistently associated with Spouse A across the App, matching the exported file; same for Spouse B.
Actual behavior: In the App UI, the displayed names appear cross-wired between spouses, but when exporting the same records, the CSV shows the correct, non-swapped values.
Request: Investigate how spouse/household relationships and primary/secondary contact ordering are being resolved in the App, confirm whether this is limited to Brentwood School or systemic, and fix any incorrect join or display logic so that UI surfaces the same name pairings as the export pipeline.
Triage Comments:
Triage: Prioritized as Medium — Brentwood School (2299) reports spouse names are swapped in the App UI while the export data is correct, indicating a display/join logic bug. The issue may be systemic across households but has a workaround (use the export), keeping it at Medium. Labeled
bug,crm-write,app-ui.