Sitewide V2: Facilities Sprint 1 Plan

[xiongjaneg]

Schedule Notes

• Michael OOO 3/28-3/29
• Alexis OOO 3/29
• Dave OOO 4/5 & 4/8

Sprint Priorities 🎯

At the end of this sprint, what do we want to have accomplished/delivered?

Tickets for top priority:

• 🎯 UX: Finalize design recommendations for Service Location Address paragraph type #17489
• 🎯 Drupal: Service location: "Unspecified" walk-ins should map to NULL following migration and should not be included in front end display #17516, Service location: "Unspecified" online scheduling should map to NULL following migration  #17518
• 🎯 FE: Analytics event inventory/audit in preparation for G4 #17532

UX

DISCUSS tracking ACs / use of epics / tasks.

• Service Location: Finalize design recommendations for Service Location Address paragraph type #17489 needs refining
• VBA: Review error states recommendations and feasibility for VBA content types #16906
• VBA/Vet Centers: Design exploration: Update Vet Center designs to include Events #15349 needs refining -- is an epic. Are we saying work this whole epic now?
  • VBA/Vet Centers: Update Vet Center designs to include Events & side nav  #17194 needs refining
    • blocked by Draft IA for Vet Centers 2.0 #17195?
• Police: Continue to update police transparency design to account for expanded contact information #17343 needs refining

Front End

DISCUSS: Analytics deadline April 5, Design system deadline for V1 deprecation where V3s exist = May 3. Progress to date indicates we need to focus on V3 adoption to hit date target. Or: push back on DS re: the deadline.

• Analytics: Analytics event inventory/audit in preparation for G4 #17532 due Apr 5
• Facility Locator: Zoom in/out buttons with NVDA activate Zoom meetings app #17409 - a11y defect 2
• Service Locations: Conditionally display "Location" header on Service Location templates #17414 - launch blocking
• V1 deprecations: Update VAMC Facility template to adopt V3 accordion component #16963 - May 3
• V1 deprecations: Update VAMC Health Services template with components (v3) #16997 - May 3
• V1 deprecations: Update VAMC Lovell with components (as needed) (v3) #17108 - May 3

Other FE work

• Facility Locator: Facility Locator search does not respect state  #16455 - actually 2 points?
• Service Locations: Office hours set to "All day open" in Drupal display as "Closed" on Front End #17415 - not launch blocking
• Adopt components: Replace content-build breadcrumb partial with V3 Component vets-design-system-documentation#2742 - 5pts
• Adopt components: Move content-build's breadcrumbs liquid logic to a liquid filter vets-design-system-documentation#2741 - 5pts
• Adopt components: VAMC Detail page: adopt V1 and V3 components where components are not used #16999 - May 3
• Adopt components: VAMC Medical Records: adopt V1 and V3 components where components are not used #16960 - May 3
• Adopt components: VAMC Operating status: adopt V1 and V3 components where components are not used #16998 - May 3
• Adopt components: Move content-build's breadcrumbs liquid logic to a liquid filter vets-design-system-documentation#2741
• Adopt components: VAMC System (incl banners): adopt V1 and V3 components where components are not used #16952
• Adopt components: VAMC Locations: adopt V1 and V3 components where components are not used #16964
• Adopt components: VAMC Register for Care (Top Task pages): adopt V1 and V3 components where components are not used #16957
• Adopt components: VAMC Billing & Insurance: adopt V1 and V3 components where components are not used #16962
• Adopt components: Staff templates: adopt V1 components where components are not used #17066
• Adopt components: Stories: adopt V1 and V3 components where components are not used #17067
• Adopt components: News Release detail page: adopt V1 components where components are not used #17068
• Adopt components: VAMC Policies: adopt V1 components where components are not used #16953
• Adopt components: VBA template: adopt V1 and V3 components where components are not used #17095

Drupal

DISCUSS: Christian working alone. Daniel or Edmund will need to be pulled in for code reviews. We will need to probably source QA on our team. We should expect a slow down as a result. 13 point suggested load may be high, even without text validation ticket.

• Spike: Remove inline entity form (IEF) from Vet Centers #17374 - discuss options for next step if needed
• Service Locations: Service location: "Unspecified" walk-ins should map to NULL following migration and should not be included in front end display #17516 - blocker
• Service Locations: Service location: "Unspecified" online scheduling should map to NULL following migration  #17518 - blocker
• Service Locations: Consider: Update Non-clinical services Views to match FE display #17381
• Service Locations: VBA Cypress test sometimes causes pipeline failures #17559

Other Drupal work

• Service Locations: Add text validation to appointment custom text in Service Location #17124 - 8 points
• Tickets that come out of Spike: Remove inline entity form (IEF) from Vet Centers #17374
• Flagged facilities when ready

[mmiddaugh]

@xiongjaneg @jilladams

Consider: Update Non-clinical services Views to match FE display department-of-veterans-affairs/va.gov-cms#17381 is listed twice under the Drupal heading, FYI
-> one other related issue in Ready is Add text validation to appointment custom text in Service Location department-of-veterans-affairs/va.gov-cms#17124 -> might this one have been intended?

Also - let's keep these two on the radar as we pushed them out of last sprint (each is 5 pts)

• Replace content-build breadcrumb partial with V3 Component department-of-veterans-affairs/vets-design-system-documentation#2742
• Move content-build's breadcrumbs liquid logic to a liquid filter department-of-veterans-affairs/vets-design-system-documentation#2741

[mmiddaugh]

UX candidate? Review error states recommendations and feasibility for VBA content types department-of-veterans-affairs/va.gov-cms#16906

[xiongjaneg]

I put 17124 back on the list. My initial concern was that it's an 8 pointer, which is concerning given Drupal capacity. There will just need to be tradeoffs.

[jilladams]

Example for the UX / ACs discussion: #17643