Design | Figma migration | Update VA design system components once fixed

[andaleliz]

Background

When migrating Sketch files to Figma, we noticed some components in the design system had a bug. The buggy components have our content in place and are placed next to the appropriate frame, ready to move in once the DST applies their fixes.

We need to update our Figma files once those fixes are in place. Since the fix tickets are in a different repo, we can't add them as blockers through Zenhub, but we can track them here:

Components

• Summary (featured content) bug ticket
• Slim error alert bug ticket

Tasks

Update the library/components in the following files:

• Connected apps
• Personal info
• Contact info
• Notification settings
• Direct deposit
• Account security
• Profile hub
• Military information

AC

• Figma files align to what we see in storybook for the available components.

[andaleliz]

@mtcA6 fyi I am going to pick this up and start working on it.

[andaleliz]

While going through this, I checked on the guidance for addresses from the design system. They've updated it and there are changes to our form as a result. I've mocked them up and annotated them on a separate page, and I think this should probably have a dedicated FE ticket as a result @mtcA6 @adamwhitlock1

The prod pages in the Figma file reflect the current state; I will move the mock-ups from the new page into the prod pages once they're live.

[andaleliz]

All of the files are updated, but I can't close this out yet due to an outstanding bug w/ the modal buttons in personal information and the editing as a subtask page. I've reached out to the DS and I'm going to give them a day or two to respond. If they don't, I think I'll still close this ticket out as it's pretty minor and I can leave a comment to explain to anyone who peeks at the files what is going on.

[andaleliz]

They still haven't gotten back to me - going to leave this open until the end of the sprint but will close Tuesday if I don't hear by then.

[mtcA6]

@andaleliz great approach.

Do we need to spin up another ticket to toss in the backlog and we can come back to that in a few weeks?

[andaleliz]

@mtcA6 nah, I don't think so - I have a feeling it'll be a 2 minute fix once they respond to me. I set a reminder on my message to them to reach back out to them before the end of the sprint, and if it happens after the fact it'll probably take more time to create/monitor tickets than to just implement whatever fix they propose.

[andaleliz]

Dan got back to me today and helped me troubleshoot. We're all good to go.