Skip to content

fix: remove duplicate Status Effective Date from record details panel - #442

Merged
mdiapenabc merged 1 commit into
devfrom
fix/record-details-last-eligibility-run
Aug 7, 2026
Merged

fix: remove duplicate Status Effective Date from record details panel#442
mdiapenabc merged 1 commit into
devfrom
fix/record-details-last-eligibility-run

Conversation

@mdiapenabc

@mdiapenabc mdiapenabc commented Aug 7, 2026

Copy link
Copy Markdown
Collaborator

Description

After merging fix/last-eligibility-evaluated-at, the record Details panel showed Status Effective Date and Last Eligibility Run stacked in the header with the same timestamp (backfill seeded last_eligibility_run_at from csa_status_effective_date). That duplicated information already available in the main table and was confusing.

Remove Status Effective Date from the Details panel header so caseworkers see only Last Eligibility Run there.

What changed

  • Removed the Status Effective Date line from the Details panel header in frontend/src/App.tsx
  • Last Eligibility Run remains in the Details header
  • Status Effective Date is unchanged in the main contacts table column

How to test

  • Open the contacts table and confirm Status Effective Date still appears as a column
  • Click a record to open Details
  • Confirm the header shows only Last Eligibility Run (no Status Effective Date)
  • Confirm Last Eligibility Run displays a formatted timestamp or -- when empty

Status Effective Date is already shown in the main table; the details header now shows only Last Eligibility Run.

@saifrazabc saifrazabc left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved

@mdiapenabc
mdiapenabc merged commit 9d14d4d into dev Aug 7, 2026
22 checks passed
@mdiapenabc
mdiapenabc deleted the fix/record-details-last-eligibility-run branch August 7, 2026 04:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants