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

FE: Handle new Operating Status options on Modernized pages - next-build #19827

Open
7 tasks
jilladams opened this issue Nov 7, 2024 · 4 comments
Open
7 tasks
Assignees
Labels
Accelerated Publishing Facilities Facilities products (VAMC, Vet Center, etc) sitewide VA.gov frontend CMS team practice area Vet Center CMS managed product owned by Facilities team

Comments

@jilladams
Copy link
Contributor

jilladams commented Nov 7, 2024

Note (11/7/24): Where this development gets done may depend on where the nextbuild template is in terms of progress. Needs to be accounted for. See ticket #19578

Description

New operating statuses need to be built and displayed correctly per final designs on modernized pages for all facility types that have been started in next-build:

  • Vet Center facility page
  • Vet Center location page

Analytics considerations

Copy any existing analytics from current operating stati

Testing & QA

QA test plan written in #19808
QA test plan will be run against the aggregate changes in FE work in #19809
QA test plan: #13598 Facility Operating Status expansion test plan

Acceptance criteria

  • Normal operating status does not display
  • Existing not-normal operating statuses display More info using the same components that are used in prod today. (No changes to slim or expandable alert.)
    • Facility notice - blue
    • Limited services and hours - blue
    • Facility closed - changes from red to yellow
  • New not-normal operating statuses display per Figma designs
  • Any behavior in final PR / build that differs from QA test plan expectations is identified, discussed with Product for signoff, and either QA test plan is updated or a ticket is created to modify that behavior to match the QA test plan
@jilladams jilladams added Needs refining Issue status sitewide VA.gov frontend CMS team practice area Vet Center CMS managed product owned by Facilities team Accelerated Publishing Facilities Facilities products (VAMC, Vet Center, etc) labels Nov 7, 2024
@Agile6MSkinner Agile6MSkinner removed the Needs refining Issue status label Nov 7, 2024
@eselkin
Copy link
Contributor

eselkin commented Nov 14, 2024

Vet Center locations is not yet built in next
Vet Center does not include the vets-website data-widget for operating statuses (it's commented out in line 195-203 of src/templates/layouts/vetCenter/index.tsx)
We will leave this ticket to last and update the Next build tickets with a reference to this ticket to identify that when those tickets are worked on that Operating Status should also get updated.

@eselkin
Copy link
Contributor

eselkin commented Nov 14, 2024

^ @jilladams

@jilladams
Copy link
Contributor Author

Deprioritized until we are ready to take on Vet Centers in next-build.

@jilladams
Copy link
Contributor Author

Needs to move into the Vet Centers next-build epic, if we can find it.

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

No branches or pull requests

3 participants