Facilities - Front End tickets

[xiongjaneg]

Front End

VBA Regional Office Pilot MVP remaining tickets

• 3 - Front End: Update Front End query for VBA Service Location paragraph type #15959 refined
• 1 - Front End: Update the VBA Facility content type query to add banner fields #14947 refined
• 3 - Front End: Front End: Add Banner fields to VBA Facility content type template #14937 refined
• 5 - Front End: VBA Other Nearby VA Locations shows the nearest VAMC, Vet Center, and Cemetery #14929 refined
• 5 - Front End: SPIKE: Front end discovery about component testing for VBA #16243 refined
• Front End: Front End testing for VBA banner #14938
• Front End: Front End testing for regional subsections for VBA Service Region #14927
• Front End: Front End testing for VBA Facility Service content type #14943
• Front End: Front End testing for VBA Service Location paragraph type #14936
• Front End: SPIKE: Document the state of VBA Regional Office testing and prep for Staging Review #15223
• Front End: Add analytics to VBA Regional office pages #16311
• Front End: Front End: Implement VBA Regional Office meta tag (SEO) #16254
• Front End: Front End: Update VAMC appointment information in Service Location #16144 cross-listed with VAMC

12/20/23 - 17pts + (8 x ~3? guesstimate til after SPIKE) = ~41 pts

Facilities API: Lighthouse V1 upgrade for other teams' consumption

• Spike: Prep for Vets-API to Lighthouse v1 updates #15000
• Update Vets-API Facilities API to use Lighthouse v1 (Phase 1)  #15344

SPIKE blocks full assessment of size / cutting remaining tickets.

Facilities products: Adopt V1 in prep for v0 deprecation remaining tickets

• 3 - FE: Update Facility app(s)/widget(s) to correctly handle API call that returns no results #12156

Other VBA tickets

• Drupal: Update Facility Locator to point to modernized VBA RO pages #14531 refined
• Drupal: Add CMS test coverage for VBA banner. #16146 refined
• Drupal: When a VBA facility name changes the section name needs to change #11628 refined
• Drupal: Winnow Facility dropdown on VBA Facility Service to match editor's Workbench Access Section #15901 refined
• Drupal: Update VBA Facility post-review and collab cycle feedback #16327
  • FE: May result in ticket
• Drupal: Add appointment fields from VAMC facility health service to Service location #16348 cross-listed with VAMC
  • FE: May result in ticket
• UX: Review Shoulds and Considers from VBA RO Pilot MVP after CMS collab cycle touchpoint #15989 refined
• UX: Design error states for VBA content types #16068 refined
• UX: Establish and enact VBA facility alias pattern #15155
• Product: VBA: Perform Foundational testing of the FE for Staging Review #16369 refined
• Product: Change management for updated Service Location impact on VAMC editors #14758 refined
• Product: Create new KB articles to support VBA editors and Regional office roll-out #14482 refined
• Product: Create runbook/checklist for VBA editors to complete pages for MVP #11304 refined
• Product: VBA RO Pilot Staging Review #16268
• Product: [Consider] Assign non-MVP VBA facilities to different section #15381
• Product: SPIKE: Determine VBA Regional Office IA implementation #15752

Police Transparency MVP remaining tickets

• UX: Enact CAIA recommendation for VAMC menu placement #16413
• UX: Determine content model for displaying VA Police contact information per facility when there are multiple numbers per system #16415
• Drupal: Implement updates to VAMC Police data page after collab cycle midpoint review #16329
  • Implement UX updates re: Police /VAMC menu placement & multiple phone #s - would be included or need sep tickets?
• 5 - Front End: FE: Finalize structure of CSV -> JSON for Police data #15722 refined
• 3 - Front End: FE: Finalize component reading data from redux for Police Transparency data #15723 refined
• 5 - Front End: Front End: Add analytics to VA Police page #16407 refined
• Front End: Back to top component for Police MVP #16414
• Front End: Front End: End to end testing and component testing for VA Police pages MVP #16438
• Product: VA Police: Perform Foundational testing of the FE, product artifact, file Platform CC ticket #16330 refined
• Product: Prep for Police Transparency collab cycle staging review #16267 refined
• Product: Change management for VAMC editors for Police pages #16023 refined

Questions:

• Is it likely the remaining UX tickets will generate new FE / Drupal tickets, or any changes are covered by existing tickets?
• To confirm: existing tickets cover implementing the components we removed from MMVP scope?

VAMC

• Front End: Front End: Update VAMC appointment information in Service Location #16144 cross-listed with VBA
• Front End: Confirm analytics implementation for VAMC "In the spotlight" links  #15693
• Drupal: Merge Mental Health phone number integration branch to main #15576
• Drupal: Service name changes should update title and alias of any service node using that service. #14731
• Drupal: Migrate VAMC Facility Service appointment information into updated Service Location #15559
• Drupal: Add appointment fields from VAMC facility health service to Service location #16348 cross-listed with VBA

Vet Centers

• Drupal: Front end: Vet Center unpublished services should not be showing on VA.gov #16362

Facility Locator

• Front End: Detect broken links in Facility Locator #16282
• Front End: FL is missing Community care substance abuse rehab facility  #16368
• Front End: Updated Lovell switch alert type should not appear on the page table of contents  #15569

Accessibility

• Front End: VAMC story and news release pagination is not announced properly #12089
• Front End: Events pagination does not have proper focus management #14755 could go at the same time as following FL pagination issues
• Front End: Facility Locator pagination Prev/Next links do not scroll to top #14895
• Front End: Implement Pagination Component  #12088

Monitoring/Testing

• Front End: Add e2e tests for Cypress on Content-build #16083
• Front End: Improve alerting via DataDog #16084

[mmiddaugh]

@xiongjaneg

• unless there is immediate application for Editors shouldn't be limited to adding only 3 Service locations #7252 (i.e. relevance to VBA), let's save it for our future selves (acknowledging that I'm the one who dredged it up to begin with)
• suggest we connect Facility phone audit report is missing some content types #14721 to the mental health phone number work somehow since that is the business need driving its prioritization
  • I assume we should also connect Create VAMC facility Phone View #15648
• suggest moving Restrict VBA RO editors from editing certain fields #15396 up in the order -> probably somewhere above VAMC services are showing too much of the service term on node view #15387 so we address the VBA items first

also, I'd like to see us get as far as we can stubbing out the tasks to complete the police data work so we can fairly evaluate the amount of work remaining and determine if we need to start making some concessions

[mmiddaugh]

@xiongjaneg @jilladams - Adding a few new items to your radar

• Update VR&E name in Facility Locator #15837
  • high priority: this change is long overdue and should be prioritized quickly
• Staff Profile sidenav accessibility defects - no label and empty list #15519
  • please see @laflannery's comment
• Standardize spotlight patterns in CMS facility content types #13804
  • If we've resolved the blockers (which in part prevented us from previously resolving the related duplicate "Read more" accessibility issue), I'd like to prioritize this to resolve the defect and to allow us to leverage the spotlight boxes to support VA health chat for a few pilot VAMC locations
• FE Provider training design implementation #15823
  • Given Max's success this past sprint, I believe we're able to now pull through the PPMS training data through to the front end
  • it will still need to be turned off but this will allow us to complete our implementation and just await sufficient data

[xiongjaneg]

@davidmpickett Is #13804 a UX ticket?

[mmiddaugh]

Feature function for Story content types only allows one Featured story #11221 - see comment

[xiongjaneg]

@xiongjaneg create a spike ticket for service region subsection

[mmiddaugh]

@xiongjaneg based on the next steps mentioned by Eli in the closed Monitoring/Testing issues #15260 and #15225, I stubbed out the following placeholder issues to give you a place to start - they can be refined/separated/edited as needed

• Add e2e tests for Cypress on Content-build Add e2e tests for Cypress on Content-build #16083
• Improve alerting via DataDog Improve alerting via DataDog #16084

I would like to know the level of effort for the testing/monitoring tasks Eli feels have the highest value

[mmiddaugh]

Unless there is a compelling reason, I don't see a need to prioritize a level 4 defect to Avoid mouse centric instructions #13937 at this time. Please let me know if I am missing important context.

I suggest either move out #14755 or pull in related issues to discuss together, including

• pagination scroll behavior
  • Facility Locator pagination Prev/Next links do not scroll to top #14895
• pagination announcement
  • VAMC story and news release pagination is not announced properly #12089
• Implement Pagination Component  #12088 (which may or may not be blocked by the design system

I'd propose swapping in a defect -1 level issue for Invalid ARIA attributes #10300 (removed based on Laura's feedback)
@laflannery is there a high value ally issue you'd recommend?

[laflannery]

@mmiddaugh I haven't been recommended or pulling forward any Drupal issues lately due to other priorities - #10300 is a Drupal issue and while it is important it is not Veteran facing.

If there is space to add accessibility issues, I would suggest the pagination issues, we have quite a few of those as you mentioned and those are the most high value FE issues currently in the backlog.

As far as the defect-4 goes - it was only suggested as a quick fix issue that could be done if someone had a small amount of time.

[xiongjaneg]

@xiongjaneg Create ticket to create widget for data for the VA Police including all the things Dave updated for the ACs for the JSON ticket and widget should accept data from content build in form of definitions from cc

[xiongjaneg]

@jilladams Check on PII in vets-api issue, will want that to be pretty stable before working on it