Open mtcA6 opened 9 months ago
@mtcA6 FYI, I'm adding Tom's ticket as a blocker. We'll need a clear understanding of what the actual rules/behavior are to write helpful content.
@mtcA6 all points for this will roll over into the next sprint
@Samara-Strauss based on the VA Profile <> MHV call that occurred today 1/3, I think it may make sense to hold off on changing the copy since it might change again very soon based on this item:
I feel like it'll be a lot of churn to proceed w this ticket and then change again if something changes. Although there is risk if we wait that the changes may happen terribly slowly.
What do you think? hold off or wait?
Yes, let's hold off until we get final confirmation from VA Profile.
minLength: 1 maxLength: 25 Allowed Characters: (case insensitive) alpha, -, ' (apostrophe), acute, grave, diaresis, cirumflex, tilde, space.
Ok so we reconfirmed the things that are allowed, I don't think the design work is stuck, we can't deploy the copy yet but we could have an updated figma file for when we are ready.
Reconfirmed by Josh L. on 1/17 new criteria:
@mtcA6 is this something you want me to try to work on this week? Happy to if, so, and if not I'll unassign myself. Thanks!
Background
we had a call with VA Profile and MHV and discussed preferred name field. it really should be preferred first name as it isn't intended for more complicated names. We should craft stronger copy detailing what is permissible in that field based on the MPI constraints
Slack Message
Tasks
Acceptance criteria