Skip to content

Clarify MMR historical dose sequence validation message#6699

Open
jhenderson wants to merge 1 commit intonextfrom
fix-mmr-upload-dose-sequence-part-2
Open

Clarify MMR historical dose sequence validation message#6699
jhenderson wants to merge 1 commit intonextfrom
fix-mmr-upload-dose-sequence-part-2

Conversation

@jhenderson
Copy link
Copy Markdown
Contributor

@jhenderson jhenderson commented Apr 27, 2026

Make the validation error for invalid MMR historical dose sequence values more consistent when uploading vaccination records.

Before this change, invalid values such as 3 and 2B could show different error messages. This change updates the wording so they now both show the same message explaining that the dose sequence cannot be greater than 2.

This is a follow up from #6560 after QA feedback.

Jira Issue - MAV-7123

@jhenderson jhenderson requested a review from a team as a code owner April 27, 2026 09:17
@jhenderson jhenderson added this to the v8.2.0 milestone Apr 27, 2026
@jhenderson jhenderson added the design tweak Small update to content or layout label Apr 27, 2026
This follows on from commit 9035a26 and QA feedback.

Update the dose sequence validation copy to use a single clearer
error message.

Jira-Issue: MAV-2312
@jhenderson jhenderson force-pushed the fix-mmr-upload-dose-sequence-part-2 branch from ba74db8 to fab5774 Compare April 27, 2026 11:15
)

dose_sequence_error_message =
"Enter a numeric which must be either #{dose_sequence_examples}."
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.

"Enter a numeric ..."? Just double-checking this is correct, it doesn't sound better to me but happy to approve if this was deemed so.

@jhenderson jhenderson modified the milestones: v8.2.0, v8.3.0, v8.4.0 Apr 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

design tweak Small update to content or layout

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants