-
Notifications
You must be signed in to change notification settings - Fork 205
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
10-10d: Feature toggle for staged release #94606
Comments
10-10d feature toggle is implemented and live on production (see in list of flippers here) |
Once I've got the confirmed yellow box copy, I'll make a small PR to address that. Beyond this, we will also need the static page copy from CAIA. |
Yellow box copy update PR here
|
Yellow box text merged in. Should be visible on staging shortly. Per this thread in DSVA, we're waiting on a doc from Laura with the static page widget content, but that shouldn't impact our ability to test that it functions. Update: The toggle is visible in staging and production |
Update: as of 10/15/2024 (when I last reached out) still waiting on the copy for static page from CAIA |
Content from Laura is here, I'll begin implementing. |
Work is done in this PR. Waiting on:
|
@baltes This is done, but we need to meet with Laura to check the widget behavior on the Drupal side. Possibly something we can talk about at today's CAIA touchpoint. |
Still blocked until we can get CAIA approval. I've reached out to Laura and am just waiting to hear back |
@baltes Per the meeting with Laura today this should be good to go. Thanks! |
As a user applying for CHAMPVA during the staged release of 10-10d, I need to be shown consistent content as determined by the flipper so that I can complete my application regardless of whether I can fill out the online form or must use the PDF form.
Acceptance criteria
(all links go to staging for illustrative purposes, but staged release will be managed in production)
When a user visits the static page and Flipper shows the user the new static page, then the user sees the link to the online form and the user can view and complete the online form
When a user visits the static page and Flipper shows user the old static page, then the user sees the link to download the PDF form AND the user does not see the link for the online form
When a user visits the online form URL directly and is not accessing it through the static page entry point, then the user should see the content shown below under Yellow box replacement text.
A product manager must be able to control all of the above conditions through the Flipper admin so that a code change is not required to move from one stage of the release to the next (e.g. moving from allowing 10% of traffic to 25% of traffic).
A meta tag is applied to block search indexing during the staged release.
The IVC forms team must be able to remove all of the above conditionals once the staged release is over and the form is 100% live.
A product manager must be able to review a fully functional toggle in staging to verify implementation.Yellow box replacement text
(new content needed)
Reach out to Jamie for guidance on any UX details for this page.
Implementation details
Engineering to add as needed...
The text was updated successfully, but these errors were encountered: