Componentization - Community care appointments - Detail View

[ala-yna]

Description

As an engineer, I want create and reuse different standardized components for appointments, so that it will easier for other teams to start working in appointments and the different appointment types can be more aligned.

Specific details of the components needed can be found in this spreadsheet (see columns F, G, H on "Details screen section" tab and also "VA Community Care - Details" tab as needed) and the design specs can be found in Figma

Note: for Community Care appointments, please be sure to use the provider location, not the associated VA facility location.

As part of this story we want to:

• Create new components that are needed for confirmed, past, and canceled, and pending Community Care appointments
• Plug in any pre-existing components
• Update end to end tests
• Update headings to match Figma file
• VQA with content/design

Acceptance Criteria

• [ ] New components have been created
• [ ] Existing components have been brought in
• [ ] E2E tests have been updated
• [ ] VQA by content
• [ ] VQA by design

[alexandec]

Approval from content and design: https://adhoc.slack.com/archives/C067S0FRP0C/p1717542786392799

[rbontrager]

@alexandec After creating a pending CC appt in Judy and talking to Misty there was a slight change to the spreadsheet that requires some code changes. The field needed under "Details you'd like to share with your provider" needs to be changed to whatever is in the [comment] and not [reason].

[alexandec]

@rbontrager I've updated the AppointmentReasonAndComment component so that for for pending CC appointments only (Canceled Pending, Pending, and Past Pending), it shows the comment field instead of the reason field

[alexandec]

@rbontrager I figured out the issue with the cancel button. Pending appointments with no cancel ID were still showing the cancel button, but the cancel button won't work without a cancel ID. I made a change so the cancel button is hidden for pending appointments with no cancel ID. This is the same approach we take for other types of appointments. I tested with Judy on staging since she has a pending appointment with no cancel ID.

I don't know if you're able to create appointments with and without cancel IDs on staging, but that would be the ideal way to test this. Alternatively you could intercept the API response in Charles and add/remove the cancel ID to test this.

[rbontrager]

Everything looks good outside of the following issues:

• CC Provider Name for non pending CC appts is not appearing on mobile. BE ticket 8806 has been made to address this.
• CC Provider Address for pending CC appts is not appearing on mobile. BE ticket 8852 has been made to address this. FE work will eventually be required and is addressed in ticket 8854
• CC VA scheduling facility name is not coming in for pending CC appts on mobile. BE ticket 8861 has been made to address this.
• Cancel request button is not appearing for Pending CC Requests. A thread is currently being discussed but it sounds like there may be an upstream bug somewhere and because of web's logic they never caught it or we have a BE bug that needs to be done.

@ala-yna Please sign off that you acknowledge these bugs and confirm you still want this ticket to be merged with them.

[ala-yna]

Thank you for the write up and follow up tickets. I agree with the decision to move this ticket forward knowing that there is follow up work to be done.