Skip to content

Fix invalid vaccination dates in already vaccinated flow#6762

Open
jhenderson wants to merge 1 commit intonextfrom
reject-invalid-dates-in-already-vaccinated-flow
Open

Fix invalid vaccination dates in already vaccinated flow#6762
jhenderson wants to merge 1 commit intonextfrom
reject-invalid-dates-in-already-vaccinated-flow

Conversation

@jhenderson
Copy link
Copy Markdown
Contributor

The "record as already vaccinated" flow from a child programme page creates a session-less DraftVaccinationRecord. In that path, draft date validation was not being enforced consistently, so invalid vaccination dates could reach the check-and-confirm step and then fail later when VaccinationRecord validation ran on save.

Update DraftVaccinationRecord so performed_at_date range validation runs during draft updates for session-less manual-report flows as well as session-backed flows.

Jira Issue - MAV-7121

Screenshots

Screenshot 2026-05-01 at 16 01 01

The "record as already vaccinated" flow from a child programme page creates a
session-less `DraftVaccinationRecord`. In that path, draft date validation was not
being enforced consistently, so invalid vaccination dates could reach the
check-and-confirm step and then fail later when `VaccinationRecord` validation
ran on save.

Update `DraftVaccinationRecord` so `performed_at_date` range validation runs during
draft updates for session-less manual-report flows as well as session-backed
flows.

Jira-Issue: MAV-7121
@jhenderson jhenderson requested a review from a team as a code owner May 1, 2026 15:41
@jhenderson jhenderson added the bug Something isn't working label May 1, 2026
@jhenderson jhenderson added this to the v8.6.0 milestone May 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant