-
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
[EPIC] Flipper audit -Identify and remove unnecessary Flippers #10656
Comments
@dsinla Walk through spreadsheet for what Facilities own, spin up individual tickets. Discuss in detail at PO sync. |
Message sent to @jilladams to get the master list |
The doc we created when went through the lists together is an XLS in sharepoint now, as that's the only way to share spreadsheets with Dave: |
Apologies for the confusion today - Google sheet link was added to our ticket, not yours. Updated the related slack thread for the histories as well. |
thanks @jilladams |
Thanks @jilladams! Going to tackle these
|
Sorry for the delay, I looked through the Facilities flippers for which ones can be safely removed. These aren't being used on the front end so they can safely be removed:
|
@maxx1128 @jilladams Does Facilities perform the removal? - or do we request some other team to remove? |
Facilities owns the code / downstream impact for those flippers, so can remove any that you're confident are ready to be removed. |
These must stay (we know they're in active use):
Likley not owned by facilities: ?
Check with Michele Middaugh - what's the history here:
|
@dsinla I just finished looking more into the two feature flags that needed more investigation and I could do right away, The functionality connected to both flags, COVID scheduling, and operational hour special instructions, have extra checks that ensure the info/functionality is first available before showing them. So if they were removed, the code would always let the info/functionality be shown if it was set. If they're ready to be turned on for everyone, then removing their code is a relatively easy change. I don't know if doing this would require any extra approval or if it's already been decided. Long story short - the code around these flags should prevent any errors if they're removed from the code and will be easy to remove. The big question is just if everyone should be allowed to see it yet. |
@maxx1128 Thanks for investigating. Regarding: |
|
|
Initial investigative report on three of the feature flags cc: @dsinla
|
Thanks @maxx1128 In comments above @mmiddaugh indicates that Note: PCAFC = Program of Comprehensive Assistance for Family Caregivers from https://www.caregiver.va.gov/support/support_benefits.asp |
Quick chat with @mmiddaugh she will take a look at covid_vaccine_scheduling_frontend |
It looks like Max has investigated the flag for covid_vaccine_scheduling_frontend. This is another situation where the functionality was built but only briefly implemented. In this case, I believe this was waiting for backend integration with VAOS. Meanwhile, the need for appointments was quickly replaced by access to vaccines on a walk-in basis so the functionality was retained but behind a flipper. |
Thanks @mmiddaugh! I think i was confusing some of the very-similar names, but would like you to weigh in on one more: facility_locator_show_operational_hours_special_instructions @maxx1128 has investigated, identified you as the owner (at one point). As with covid_vaccine_scheduling_frontend we want someone with more background to weigh in before we remove it. |
@jilladams I'm confused why this is in the Current Sprint, Not started column for Facilities. Seems like a mistake |
Yep, something got weird in workflow connections between boards, thanks for flagging. removing. |
Description
All the detail in previous ticket: Follow up from #10350
List of flippers and owners: https://docs.google.com/spreadsheets/d/1yQb5oDshNj7y0nvtF3PaZ9OLhtTuZ2aO8t4_n51YBWU/edit#gid=237722104
Tracking here for at-a-glance status
Acceptance Criteria
The text was updated successfully, but these errors were encountered: