Open natalia-fitzgerald opened 1 month ago
@angelcardoz @dan-padgett The following reflect the designs we discussed for the phone extension.
Desktop | Mobile |
---|---|
Thanks @natalia-fitzgerald! Since this is just an addition to phone number, I'll check off the validation task.
The front end has now implemented the design shown here. The backend and the front end have been set up to accept 254 max characters (letters, numbers, or special characters).
There is a product owner preference to stay as close to the stakeholder request as possible which is to add a field that's strictly for phone extension. There are concerns with accommodating 254 characters as it could lead to unintended consequences. One concern is that we open up the field to inadvertently collecting PII.
I have discussed with development and, in a future sprint, we can prioritize making a change to more tightly define the number of characters (11-15 or some number we define). This change will require backend, frontend, content, and design work.
@angelcardoz - Do we want to release this within this sprint the way we have it and then make an adjustment in a subsequent sprint?
@natalia-fitzgerald, we can release the way we have it, but would like to make the changes next sprint.
Most up-to-date mock-ups can be found in Figma - Provide filing details step.
Default
Error
Updated after dev/design sync
Epic
Epic issue includes overview, complete list of user stories, technical and content requirements, user testing task ideation, and current design mock-ups.
User story
Acceptance criteria
Technical tasks
Team members should create technical tasks and add links (below) prior to sprint planning.
UX
Content
Front end
Back end