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

Evaluate flipper caregiver_use_facilities_API for removal #11601

Open
3 tasks
dsinla opened this issue Nov 16, 2022 · 1 comment
Open
3 tasks

Evaluate flipper caregiver_use_facilities_API for removal #11601

dsinla opened this issue Nov 16, 2022 · 1 comment
Labels
Facilities Facilities products (VAMC, Vet Center, etc) Needs refining Issue status sitewide VA.gov frontend CMS team practice area

Comments

@dsinla
Copy link
Contributor

dsinla commented Nov 16, 2022

Description

Investigate facility_locator_restore_community_care_pagination flipper for current use and eligibility for removal.

Refer to #10656

Tasks

Preview Give feedback
@dsinla dsinla added the Needs refining Issue status label Nov 16, 2022
@github-actions github-actions bot added the Facilities Facilities products (VAMC, Vet Center, etc) label Nov 16, 2022
@dsinla dsinla added the VA.gov frontend CMS team practice area label Nov 16, 2022
@dsinla dsinla changed the title Establish criteria to remove flipper caregiver_use_facilities_API FE: Establish criteria to remove flipper caregiver_use_facilities_API Nov 16, 2022
@dsinla
Copy link
Contributor Author

dsinla commented Nov 17, 2022

Relevant detail from this slack chat below

David Shannon
@matt Long I work with @dawn Pruitt on the Facilities team. As a follow up, can you speak to the eventual criteria/plan to remove this flipper, and the one for HCA? We're trying to improve our process, and we want every flipper (ideally when created) to have a corresponding removal issue created and linked as well. Seems like the plan would be - once verified and tested as part of MVP - to remove the flipper for both apps and integrate the LH API as part of production . Is that correct?

Matt Long
@david Shannon, I can. So we’ve tested, as part of the MVP, that we can get the data we would need to suffice an implementation. We are now in the process of determining the best user experience and design that would fit the implementation.
Our plan is to get an approved UX design with our stakeholders, implement that within the form, go through a QA process and then roll out to production in a controlled fashion.
The controlled implementation would be a 25, 50, 75, 100% rollout over a 4-week period to ensure we have zero issues. At the end of that 4 week roll out period we would remove the toggle.
Additionally, per our stakeholder requirements.. we are awaiting the release of the LH v1 API for facilities that adds additional info in the API response that our stakeholders are looking for. Hence the delay between the creation of the MVP and the advancement of this project.

@Dottisea Dottisea added Public Websites Scrum team in the Sitewide crew and removed Facilities Facilities products (VAMC, Vet Center, etc) labels Feb 15, 2023
@FranECross FranECross added Facilities Facilities products (VAMC, Vet Center, etc) and removed Public Websites Scrum team in the Sitewide crew labels Jan 24, 2024
@Agile6MSkinner Agile6MSkinner changed the title FE: Establish criteria to remove flipper caregiver_use_facilities_API Evaluate flipper caregiver_use_facilities_API for removal Jul 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Facilities Facilities products (VAMC, Vet Center, etc) Needs refining Issue status sitewide VA.gov frontend CMS team practice area
Projects
None yet
Development

No branches or pull requests

4 participants