[DESIGN] Create error state for when travel link cannot be retrieved

[cgednalske]

Background

Based on this discussion, we'll need an error state for when a when there’s an error fetching the travel claim link from the api.

Appointments team already has this in place for AVS, which we should likely follow while ensuring this does not present any new page concerns: AVS error state pattern

Some questions to consider:

• Do we need something in the travel reimbursement section only?
• How will we treat the action link section? Is something needed there as well or does that link disappear?
• Which scenarios does this apply to?

(Reach out to John W. and Simi with any questions)

Tasks

• [ ] Create any needed error frame states
• [ ] Review with CIE UX and Peter/Appointments UX
• [ ] Update feature and latest designs

A/C

• [ ] Error states created and added to appropriate Figma pages
• [ ] Solution reviewed with CIE UX and Peter/Appointments UX

[zach-park]

Hey team! Please add your planning poker estimate with Zenhub @cgednalske @StevenStraily

[loripusey]

@zach-park if you guys are going to continue to use Planning Poker (which is a ZenHub feature that will be going away towards the end of the year), please remember to copy the estimate into the Estimate field for the ticket inside the GitHub project.

[cgednalske]

We can probably just comment here in the ticket or in a related Slack thread moving forward.

My vote was a 2‍⃣

[cgednalske]

@zach-park @StevenStraily want to add your estimates?

[StevenStraily]

I voted 3 in the poker.

[cgednalske]

@loripusey This ticket is more important than the breadcrumb ticket, so if we need to take anything out, we can remove the breadcrumb ticket and @zach-park can work on this one instead.

[cgednalske]

Based on our pointing discussion, proposing this is a 2‍⃣

[zach-park]

FYI, FE ticket: https://github.com/department-of-veterans-affairs/va.gov-team/issues/96580