Facilities team testing for VAMC/VBA Service Locations changes

[xiongjaneg]

Description

When dev is complete on the VAMC/VBA Service Locations changes, the team will synchronously test and capture any defects.

This ticket will track those issues in comments for review & triage, to determine priority.

• Tugboat links:

  • Tugboat env: https://tugboat.vfs.va.gov/65255ca9c573c9cdb2d06792
  • CMS: https://pr15622-xptmfsnjoodldn85nzgkrgljqtfbz24b.ci.cms.va.gov/
  • Web (front end): https://web-xptmfsnjoodldn85nzgkrgljqtfbz24b.ci.cms.va.gov/

• Once prioritized to be fixed, issues will get added to VAMC/VBA Service Locations punch list for fixing issues #17454

Issues

• Service location: "Unspecified" referral should not be included in front end display #17513
• Facility address should not be displayed on FE when editor selects "Use the facility's street address" #17514
• 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
• Hide Service Options and Appointments fieldsets on Non-Clinical Services #17515

[davidmpickett]

@xiongjaneg @mmiddaugh This ticket is not launch blocking or high priority since Service Regions will not be entered by local staff and the functionality works, it's just formatting #17481

[davidmpickett]

@xiongjaneg @mmiddaugh Slightly higher priority, but still low because Service Regions will have limited users. Just wanted to make sure we had a placeholder in the backlog #17482

[davidmpickett]

@mmiddaugh @xiongjaneg Another low priority ticket about Service Region #17512

[davidmpickett]

@xiongjaneg @mmiddaugh Here's my first find that might be worth considering prioritizing. Don't think it would be launch blocking, but could be something we want to run shortly after launch. #17515

[davidmpickett]

@xiongjaneg @mmiddaugh And here's a basic stub for the thing I was talking about during the meeting today about having a way to reduce the number of "Unspecified" in the future. Definitely not an immediate action item, but pulled up some comments from a previous ticket

[jilladams]

@xiongjaneg @mmiddaugh for the purposes of Sprint 105 reporting: we've got an issue list, and I know y'all have collaborated on prioritization. Thoughts on whether or not this ticket can / should close?

[xiongjaneg]

Yes, tickets have been moved to follow up issue for priority. Closing.