Facilities Team Refinement

[xiongjaneg]

Q2 priorities:

Tickets for refining. Lists do not include previously refined tickets.

Priority Injections (?)

1) V3 component adoption - May 3 deadline - #17653

• Tickets complete, deadline met unless bugs arise after May 3 cutover

• Adopt spotlight-card class on spotlight cards on Vet Centers and VBA #18126

2) va-icon adoption - end of May deadline - #17722

• 🟢 FE work is refined
• 🟡 Encountering small blockers along the way

4) Lighthouse V1 / FL update to adopt - currently, June 1 deadline - #14507

• Our ticket 15344 should be resolved by IIR-#540
• Facility Locator detail pages: migrate to V1 #18183 - waiting on IIR confirmation they'll handle

5) Service Location Enhancement launch blockers - #16825

• 🟢 Launch is complete
• Product: VAMC editor communication follow-up to Service Location launch #18145 - Jill / Dave / Michael to refine async

6) VBA Staging Review Blockers - #16268

• Team: VBA RO Bug bash #18159

VBA Pilot remainders - #10514

• FE/UX: VBA final design review #17966

7) VA Health Chat and VA Health Connect - #15037

• 🟡 Blocked on VHA DM
• UX: Update design based on research findings for VA Health Chat and Health Connect #16009 -- not critical to refine now, bc this initiative is delayed.

8) FL Provider Core Training search/ filters - #14225

• Need to scrub the epic for next steps tickets to refine

9) V1/V3 component adoption for impostor components #17655

10) Vet Center inline editor / allow only one / winnower - #17708 / #7818

These tickets are not in priority order yet. We may want to do a product level kickoff before we try to refine them.

• Drupal: Cross-product: Remove already created services from the options when adding a new service #17674
• CM: Content model? #17733
• Drupal: Make required services unable to be removed or archived #17676
• Drupal & FE: SPIKE: Is Vet Center FE query/template based on IEF logic? Or will it work as is? #17681. -- need some addl Drupal specifics in order to assess FE impact
• Drupal: Add new Services View into Vet Centers node and remove IEF #18003 - this is the launch step, and needs re-refined when other epic tickets are done
• Drupal: Vet Center services added through IEF bypass allow_only_one_validation #5981 - icebox?
• Drupal: Last updated by human not set when Vet Center Service is saved/updated. #15124 - icebox?
• Drupal: Revision log message on Vet Center Services are misleading #15125 - icebox?

11) Vet Centers design iteration (2.0) - #17661

• 🟡 Need Product work to get the Epic in shape re: scope after Jordan's research review, plan out next steps work, etc.

13) Mobile VAMC design - #12923

• 🟡 When Amanda has concluded research review, need to revisit UX scope to cut Research, Design & potentially Content Modeling tickets. (Research review has no ticket. Thoughts?)

14) VBA Regional Office National MVP - #14477

• Will create new Editor research tickets as needed.
• Need to review issues in epic for whether they qualify as bug fixes found during launch / training cycles, or as enhancements that push to post-MVP epic.

18) Facility Locator: "Service type" field iterations - #15541

• DOUBLE CHECK for more tickets to be refined

20) Improve services accordions & locations across products - #17350

• Drupal: Consider: Conditionally require field_clinic_name on Service Location Address #17380
• [Retire?] Telehealth in VA Services #17974
• Drupal: VAMC/VBA: Add new fields to Service Locations Audit #17497

Other Q2 priorities

• 🟡 MHV on VAMC sites #12942 -- no product details yet
• 🟡 Police transparency MVP #14327 -- generally: blocked on Axon data next steps
  • Drupal: Implement expanded police contact information model in Drupal #16813 - can be refined
• FL plain language services search #15541
  • Update Facility Locator to allow plain language search for VA health services via Lighthouse V1 (Phase 3) #14993

Other work (not Q2 prioritized)

#18031

Candidates for injection?

Other

• Analytics: Confirm VAMC analytics #16389
• Drupal/UX: VAMC: Prevent VAMC editors from adding duplicate mental health number in mental health service accordion #17397
• FE: Update Facility Locator fields to be the same height #17836 - repros after typography merges?
• Phone number epic [EPIC] Standardize phone number entry in Drupal interfaces #17854 - contains several Drupal & FE tix that need refining
  • Drupal: Add server-side validation on ext field in phone paragraph in Drupal #17863

[mmiddaugh]

Additional candidates:

• #16148 Update phone numbers in Facilities products to use component
• Update police transparency FE design to account for expanded contact information #16810
• [ADD] VA police to VA Service Taxonomy #16811
• Draft detailed content spec for expanded police contact information #16812
• Implement expanded police contact information model in Drupal #16813
• Update FE query and template for expanded VA police contact information #16814

[xiongjaneg]

@xiongjaneg create launch ticket for this change

[mmiddaugh]

@laflannery found these accessibility defects - which has the highest value?

• FE: Update phone numbers in Facilities products to use component Update phone numbers in Facilities products to use component #16148
• FE: Updated Lovell switch alert type should not appear on the page table of contents Updated Lovell switch alert type should not appear on the page table of contents  #15569
• FE: VAMC event, story, and news release pagination is not announced properly VAMC story and news release pagination is not announced properly #12089

@xiongjaneg suggestions for group discussion:

• Standardize spotlight patterns in CMS facility content types Design: Standardize spotlight patterns in CMS facility content types #13804
• Remove Featured field order from featured fieldset Remove Featured field order from featured fieldset. #13688

[laflannery]

@mmiddaugh I would say the Lovell switcher we should tackle first, that might take some creativity. The other 2 are related to the overall component work we are doing so those would start that work of getting everything updated properly

[xiongjaneg]

@laflannery For #13804, is that one ready for pre-refinement for Front End or do you want to discuss in UX sync first?

[laflannery]

@xiongjaneg It's ready but it's not an engineering ticket, it's a UX ticket to standarize/create the pattern, then from that would be follow up engineering tickets

[xiongjaneg]

Thanks @laflannery that's what I thought. @davidmpickett could we get #13804 on the agenda for next UX sync. Thank you!

[mmiddaugh]

Related issues

• Should we include Front end changes and associated tests for Address module upgrade to version 2 department-of-veterans-affairs/va.gov-cms#17193 along with Drupal: back end changes and associated tests for Address module upgrade to version 2 department-of-veterans-affairs/va.gov-cms#17191?

Priority front end tasks

Front end pre-refinement

• VAMC: FE: Update GA event label for secondary CTAs (VAMC) #17237
  (suggest replacing with Incorrect heading level for "Manage your health online" #12079 - an a11y-defect-2)
• Defect: Map thumbnails for Vet Center CAPs do not render on the locations page #15656
  (suggest replacing with Update twitter logo on VAMC pages #15390 - identified VHA DM priority)
• #17107 Front end: Implement Lovell Cerner (Oracle Health) changes
  • Can we please confirm that no tests should be added/updated with the Cerner/Oracle health change?
  • Do we need an issue for testing the implementation in staging?

Other considerations

• Drupal
  • [CONSIDER] Temporary location override department-of-veterans-affairs/va.gov-cms#17144
• Front end pre-refinement
  • Fix inconsistent logic in VAMC pages display of Top task links is somewhat related to Lovell Tricare URL changes department-of-veterans-affairs/va.gov-cms#17299

[davidmpickett]

I don't know that #15608 is actionable. We haven't implemented that feature, it's been on hold.

[jilladams]

#17566 was removed but will block VBA staging review. Dave to keep refining and we'll come back to it.

[davidmpickett]

@jilladams FYI - I added sections here for Service Location and VBA launch blocking tickets.

[jilladams]

Ticket's been expanded to be full team, so includes UX tickets as well.

[jilladams]

#17791 need to add for FE

[mmiddaugh]

@jilladams @davidmpickett The following defects should also be in the queue:
Missing Multi-specialty PPMS Provider department-of-veterans-affairs/va.gov-cms#17547
Changes to the location search parameter in a Community care search traps the user department-of-veterans-affairs/va.gov-cms#15664 - A11y defect 2

[jilladams]

Removing 2 sections per updates to Q2 priorities:

12) Multiple photos for facility pages - #15718

• UX: Design: multiple facility photos #16719
• UX: Design: FE for event page using more than one image #17254
• UX: Design: FE for story page using more than one image #16890

15) Featured Stories rethink - #11401

• UX: [DISCOVERY] Editorial process: Story content #13914 - is this the right ticket to start UX thinking?
• CM: May need a ticket, tbd
• Drupal & UX: [CONSIDER] New possibilities for Featured Stories #13695 - may be a good starting point to review options? Or: we may not want to bias process / may want to start greenfield with UX.

[mmiddaugh]

@jilladams @davidmpickett
For refinement consideration:

• Re: Facility Locator: "Service type" field iterations: I believe there is some design layout work to implement progressive disclosure for the Service type field following meetings with the Design system team - this may not yet be ticketed.

• FE: [VAMC] Veteran-facing navigation experience between system and facility level health service #13910- this is a VHA priority, would be good to validate my assumption that this is a small lift and have it ready for a future sprint

• Drupal work to move to implement separate phone number and extension fields

[aklausmeier]

Re: Facility Locator: "Service type" field iterations: I believe there is some design layout work to implement progressive disclosure for the Service type field following meetings with the Design system team - this may not yet be ticketed.

#17835 - related ticket has been created

[davidmpickett]

Noting that priority 19 has been removed from last as that is being transferred to IIR
#17748

[davidmpickett]

@jilladams @davidmpickett For refinement consideration:

• Re: Facility Locator: "Service type" field iterations: I believe there is some design layout work to implement progressive disclosure for the Service type field following meetings with the Design system team - this may not yet be ticketed.

#17835 is refined and candidate for Sprint 3

• FE: [VAMC] Veteran-facing navigation experience between system and facility level health service #13910- this is a VHA priority, would be good to validate my assumption that this is a small lift and have it ready for a future sprint

I updated the ticket to reflect the new scope and added it to list here for refinement.

• Drupal work to move to implement separate phone number and extension fields

Phone number epic is at the bottom of the list and I added the ticket from that epic that Jill, Laura, and I identified as a quick win as a first one to refine.

[jilladams]

Sticking this here bc I still think of this ticket for now: #18214 (comment)

[Agile6MSkinner]

@jilladams are you ready to move on from this ticket?

[jilladams]

Have goldfish, ready to travel wherever you're headed. Closing.