Skip to content
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

Closed
4 tasks done
davidmpickett opened this issue Apr 30, 2024 · 12 comments
Closed
4 tasks done

Add new Services View into Vet Centers node and remove IEF #18003

davidmpickett opened this issue Apr 30, 2024 · 12 comments
Assignees
Labels
Drupal engineering CMS team practice area Facilities Facilities products (VAMC, Vet Center, etc) sitewide Vet Center CMS managed product owned by Facilities team

Comments

@davidmpickett
Copy link
Contributor

davidmpickett commented Apr 30, 2024

User Story or Problem Statement

Final Drupal implementation

Description or Additional Context

Steps for Implementation

  • Create the new view
  • Follow design for "Add new service" button implementation, and to pass a token to Vet Center - Facility Service so the Facility is pre-populated
  • Update Vet Center content type to embed this view
  • Remove IEF from Vet Center

@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

  • Editors can see the existing Facility Services for their Vet Center while editing their Vet Center
  • Editors can see what services are required vs. not
  • Editors can see the moderation state of a listed Vet Center facility service
  • Editors can click out to a Vet Center facility service to edit
  • Editors can click the "Go to services" button in their dashboard and be taken directly to the relevant part of the Vet Center node edit
  • Appropriate services display on FE of Vet Center (no regression)
  • SHOULD NOT MERGE until Change Management is coordinated - Change management for Vet Center IEF / allow only one changes #17840
  • Requires design review
  • Requires accessibility review

Close Child Tickets

  1. CY24-Q2 Defect Drupal engineering Facilities Vet Center sitewide
    omahane
  2. CY24-Q2 Defect Drupal engineering Facilities Vet Center sitewide
    omahane
  3. CY24-Q2 Defect Drupal engineering Facilities Needs refining Vet Center crew-sitewide sitewide
    omahane

Unblock follow up FE ticket

  1. 2 of 2
    Defect Facilities Technical debt VA.gov frontend Vet Center sitewide
    eselkin
@davidmpickett davidmpickett added Drupal engineering CMS team practice area Facilities Facilities products (VAMC, Vet Center, etc) Needs refining Issue status Vet Center CMS managed product owned by Facilities team labels Apr 30, 2024
@jilladams jilladams removed the Needs refining Issue status label May 23, 2024
@jilladams jilladams changed the title Add new Services View (via form_alter) to Vet Centers Add new Services View to Vet Centers May 23, 2024
@jilladams jilladams added the Needs refining Issue status label May 23, 2024
@davidmpickett davidmpickett changed the title Add new Services View to Vet Centers Add new Services View to into Vet Centers node and remove IEF May 30, 2024
@davidmpickett davidmpickett changed the title Add new Services View to into Vet Centers node and remove IEF Add new Services View into Vet Centers node and remove IEF May 30, 2024
@jilladams
Copy link
Contributor

8 point estimate for engineering; 5 points for standing up env / testing / support & verification

@Agile6MSkinner
Copy link

Agile6MSkinner commented Jul 1, 2024

#15125
#15124
#5981

Can be closed when this one is. Added a task list to track that.

@Agile6MSkinner Agile6MSkinner removed the Blocked Issues that are blocked on factors other than blocking issues. label Jul 1, 2024
@jilladams jilladams removed the Needs refining Issue status label Jul 10, 2024
@jilladams
Copy link
Contributor

Change management info is updated in #17840 and target is 8/15, so this will roll into Sprint 10. @omahane best to plan some time around then for refreshing the PR to get updated to main / passing tests, etc.

@jilladams
Copy link
Contributor

Updated branch on this PR and moved it to Ready to review. We can merge tomorrow after daily deploy if CI passes.

@jilladams
Copy link
Contributor

Comms went out to editors for CM last night. PR is now merged. Moving to prod verify.

@jilladams
Copy link
Contributor

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.

@davidmpickett
Copy link
Contributor Author

Verified the following on Clarksville Vet Center

  • Services area shows up in appropriate spot on Node:Edit of Vet Center
  • Service names are linked to Node:View of correct Services
  • Edit buttons open Node:Edit of correct Service
  • Add service button correctly pre-populates Vet Center and Section fields on Node:Create for Service
  • All links open in new tab

@davidmpickett
Copy link
Contributor Author

Verified on Vet Center dashboard for Clarksville

  • Clicking the Go to Services button directly jumps the user top the Services part of the correct Vet Center

@davidmpickett
Copy link
Contributor Author

Verified on Staging for Clarksville Vet Center

  • Adding an Optional service shows up correctly as optional on Service list
  • Required Services cannot be Archived
  • Optional Services can be archived

Screenshot 2024-08-19 at 1 48 12 PM

Screenshot 2024-08-19 at 1 50 03 PM

Screenshot 2024-08-19 at 1 50 23 PM

@davidmpickett
Copy link
Contributor Author

One small regression, the Jump to edit link at the top broke because the id for the Services area changes from
#edit-field-health-services to #edit-group-vet-center-services

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.

@davidmpickett
Copy link
Contributor Author

And here's that ticket: #18953

@davidmpickett
Copy link
Contributor Author

Closing as complete and verified

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Drupal engineering CMS team practice area Facilities Facilities products (VAMC, Vet Center, etc) sitewide Vet Center CMS managed product owned by Facilities team
Projects
None yet
Development

No branches or pull requests

4 participants