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

Replace IEF for facility status on Operating Status form. #6849

Open
10 tasks
kevwalsh opened this issue Nov 1, 2021 · 1 comment
Open
10 tasks

Replace IEF for facility status on Operating Status form. #6849

kevwalsh opened this issue Nov 1, 2021 · 1 comment
Labels
crew-sitewide Drupal engineering CMS team practice area Enhancement Issue type: New feature or request Facilities Facilities products (VAMC, Vet Center, etc) ghp-backlog jpa-1 points-5 sitewide VAMC CMS managed product owned by Facilities team

Comments

@kevwalsh
Copy link
Contributor

kevwalsh commented Nov 1, 2021

User Story or Problem Statement

As an editor of Operating Status, i want to see my facilities' operating status all in one place, with links to edit them, but i don't want the added confusion of an "inline entity form".

The entity reference field on VAMC Operating Status has been depracated on the FE by department-of-veterans-affairs/content-build#710 (but we assume that listing facility statuses here is still useful).

ACs

  • Entity reference field has been removed
  • Remove the IEF edit mode for Facilities, which is no longer needed
  • Remove IEF tableview from codebase, which is no longer needed
  • New view list to mimic the fields visible on www.va.gov/pittsburgh-health-care/operating-status has been placed in the fieldgroup, along with an <a href="/node/NID/edit">Edit</a> (Opens in a new tab) column.
    • View of VAMC facilities
    • Title, Facility status, Edit
    • Filtered for facilities where NID forfield_region_page matchesthe NID for field_office from the Operating status page
  • Design review
  • Check with @xiongjaneg about the need for KB or Training updates that may be required.
  • Change management implications have been considered and planned for (likely would benefit from some lite in-application messaging).
@kevwalsh
Copy link
Contributor Author

@ethanteague i think this is going to be tricky and may require some discovery both on design and engineering.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
crew-sitewide Drupal engineering CMS team practice area Enhancement Issue type: New feature or request Facilities Facilities products (VAMC, Vet Center, etc) ghp-backlog jpa-1 points-5 sitewide VAMC CMS managed product owned by Facilities team
Projects
None yet
Development

No branches or pull requests

5 participants