BUG - Sev-3- All - Can still update mailing address in letters when the contact-info endpoint is blocked/down

[rbontrager]

What happened?

You can still update the mailing address in letters when the contact-info endpoint is blocked/down.

Specs:

• Device:
• OS:
• User Account:
• Accessibility State:

Steps to Reproduce

1. Block/error out the contact-info endpoint in charles proxy
2. Navigate to contact info. Verify that a you can't connect to the network error is displayed
3. Navigate to benefits > VA letters and documents. Click on mailing address. Notice that in charles it calls the blocked endpoint but still lets you update the mailing address.

Desired behavior

Acceptance Criteria

Bug Severity - BE SURE TO ADD THE SEVERITY LABEL

See Bug Tracking for details on severity levels

• Impact: High Low
• Frequency: High Low

• 3 - Low
• 2 - High
• 1 - Critical

Linked to Story

Screen shot(s) and additional information

Full JSON response for services related to issue (expand/collapse)

Ticket Checklist

• Steps to reproduce are defined
• Desired behavior is added
• Labels added (front-end, back-end, global, Health, relevant feature, accessibility, etc)
• Estimate of 1 added (for front-end tickets)
• Added either to the relevant feature epic (if found during new feature implementation), or the relevant team's bug epic (Global, Health & Benefits, API, QART)

[matt-guest-wilcore]

BUG.SEV.3.-.10095.Recreation.mp4

Hi @rbontrager, I just need some clarification for this ticket. Here's a video of me reproducing it by following the steps mentioned in this issue. When we get to the mailing address and click on it should we not see the edit screen come up at all? Also, if the user encounters this error, shouldn’t we display an alert to avoid confusion?

[jennb33]

12/10/2024 - Matt is still waiting to hear back from Rachel Bonetrager

[rbontrager]

@matt-guest-wilcore I'm not qualified to answer that question because this was one of those tickets where we planned to sit down with our UX/content to hash out the desired behavior. @wavelaurenrussell @mistymg Would you mind taking a look at this ticket when you can and giving us an outline of what you want to see in the case above.

[wavelaurenrussell]

Tagging myself as @wavelaurenrussell since I don't have access to that other account!

[mistymg]

@matt-guest-wilcore This bug isn't ready yet for engineering to work on. It needs investigated by UX/Content. We'll make our own tickets for our backlog to be added in an upcoming sprint when we have capacity. Until then, I'd consider this ticket blocked.

[jennb33]

12/10/2024 - moved ticket to blocked status on MFS board due to the work that still needs to be done on this ticket.

[jennb33]

12/11/2024 - removing ticket from Sprint 6 until it has been unblocked by UX/Content from Flagship.