-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VAMC Billing & Insurance: adopt V1 and V3 components where components are not used #16962
Comments
I estimate this ticket at a 3 for moving over a good amount of relatively simple elements over to components (deja vu) |
I removed the link component from this ticket, after working with PW, the link I noted on this page is CMS content and we are limited with what we can do with that type of content |
Telephone moved to #16148 |
2, Links will be handled by #16957 (similar to Records ticket) |
@eselkin You mentioned in scrum you merged this, so I just checked and confirmed its on Prod, excellent. But for bookeeping purposes - I can't see a PR mentioned anywhere. Is that OK, not OK, should there be? |
@laflannery Of course it's because I linked the zenhub ticket not the github ticket. Let me fix it department-of-veterans-affairs/content-build#2064 It's in prod: https://www.va.gov/northeast-ohio-health-care/billing-and-insurance/ |
Closing as Eli and I have both verified on Prod |
Description
VAMC Billing & Insurance pages need the following updates to components:
Example pages:
Elements that are not using components that should be (Backlog)
TelephoneThe first phone number, for copay questions, is not using the component but should be using the v1All other phone numbers are using the correct componentWe should confirm that Exts in phone numbers within the component are parsed correctlyLinkFacility names should use the link componentAcceptance Criteria
The text was updated successfully, but these errors were encountered: