hdjustice
commented
2 months ago Can we look at these for both short term and long term?
- Short term being anything we can do to reduce the issue for CG staff now (like field validation, adding a "Country" field, etc) with very little work (less than a day is ideal)
- Long term being adding the county validation, per Mitch's suggestion
for County, we also talked a while back about making that a dropdown, right? now that we know we have a table for that (thanks, Income Limits export from VES!) the dropdown option is squarely on the table. this means the only location info at all is the State ID, but once the State is selected we can filter by that FWIW every single county name is unique per state. ... EXCEPT for St. Louis, which has two Counties with the same name in Missouri :sob-rotating: they differ by description: "The county of St. Louis" vs "The independent city of St. Louis"
jessicastump
Issue Description
What details are necessary for understanding the specific work or request tracked by this issue?
Benefit to the Veteran
The county field placed in the address block is unexpected per user's mental model and causes confusion.
Where
Aug 30, 2024 | Va.gov Touchbase: Meeting with VA.gov, CSP, SPS, and MuleSoft Team. This came up during the stakeholder calls that they are getting users inputing in Country not County and causing work on the back end to fix.
Why
To alleviate and reduce confusion by Veterans and Caregivers completing the online form and to reduce back end corrections needed.
What
Explore design and content options in Figma to review with team.
Tasks
Acceptance Criteria