Closed andaleliz closed 1 year ago
@mtcA6 I'm adding this to sprint 17 but likely will carry over into sprint 18 too.
@adamwhitlock1 do we have separate alerts for missing unit number and bad unit number?
In Sketch, I have mock-ups for two different alerts (missing, bad)
However, it looks like in our use case docs, we combined the bad unit number w/ the address not found alert.
I'm not sure which one is aligned to what we have in the code. Could you please check and lmk when you have a chance? Thanks!
@mtcA6 FYI: I'm carrying over 2 points for this into sprint 18
Looked into these alerts @andaleliz. Here is what we have in the code:
Bad unit number
U.S. Postal Service records show that there may be a problem with the unit number for this address. Confirm that you want us to use this address as you entered it. Or, cancel to edit the address.
Missing Unit
U.S. Postal Service records show this address may need a unit number. Confirm that you want us to use this address as you entered it. Or, go back to edit and add a unit number.
Then we have the regular alerts for if there is a suggestion or no suggestions that come back from the validation service:
Suggestion
Tell us which of these addresses you’d like us to use.
No suggestion
We can’t confirm the address you entered with the U.S. Postal Service. Confirm that you want us to use this address as you entered it. Or, go back to edit it.
So it looks like they are separate
Thanks @adamwhitlock1, I've updated the use case docs to reflect that and will be sure Sketch aligns accordingly.
I've completed the updates - going to review with Pam and Angela on Tuesday, and then the rest of the team later in the day. Moving to validate until then.
User flow is updated with the feedback received from the team (not including changes to desktop) and the use case docs have been updated.
Thanks @andaleliz I've loved watching the progression of all of these.
Background
The team determined that the user flow approach piloted in the notification settings mobile Sketch page (review MHV on VA.gov section) is helpful across all practice areas, and an improvement over the current high level user flows.
In #61356 we refined that approach and are ready to apply it to other parts of profile. Let's apply this to the mobile pages only, not desktop. It's duplicative to do it in both places, and we are a mobile-first organization.
Tasks
Output
Flow diagram