-
Notifications
You must be signed in to change notification settings - Fork 70
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
Add new Services View into Vet Centers node and remove IEF #18003
Comments
8 point estimate for engineering; 5 points for standing up env / testing / support & verification |
Updated branch on this PR and moved it to Ready to review. We can merge tomorrow after daily deploy if CI passes. |
Comms went out to editors for CM last night. PR is now merged. Moving to prod verify. |
Changes have deployed and are live in prod: https://prod.cms.va.gov/node/3784/edit I haven't gone through full verification, so we will need some help to do UAT for end of sprint just to verify that everything's correct live, and we can close this. |
Verified the following on Clarksville Vet Center
|
Verified on Vet Center dashboard for Clarksville
|
Verified on Staging for Clarksville Vet Center
|
One small regression, the Jump to edit link at the top broke because the id for the Services area changes from I know that we talked about spinning up a dedicated ticket for addressing all the Anchor Links on the Vet Center content types after @laflannery's feedback on the Mission explainer ticket. I am comfortable having that fix be part of that ticket. |
And here's that ticket: #18953 |
Closing as complete and verified |
User Story or Problem Statement
Final Drupal implementation
Description or Additional Context
Steps for Implementation
@davidmpickett says "Consider splitting creating the View into it's own ticket and letting this one serve as the step where you embed it in Vet Center content type and remove IEF"
@omahane said "Nope, has to go together"
Acceptance Criteria
Close Child Tickets
Unblock follow up FE ticket
The text was updated successfully, but these errors were encountered: