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

VACMS-17854: Add feature toggle to display old/new telephone fields conditionally #19472

Conversation

dsasser
Copy link
Contributor

@dsasser dsasser commented Oct 9, 2024

Description

Moves the new telephone migration fields behind a feature toggle.

Relates to #17854

Testing done

Manual

QA steps (happy path, full QA happens here)

Run the migration (daily, once; check the telephone audit View and/or the Codit Batch Operations logs to see if the migration has been run by someone else before running)

Get a terminal in the tugboat
Run the following commands:

time drush codit-batch-operations:run MigratePhoneFieldToParagraph &&
time drush codit-batch-operations:run MigrateVamcBillingInsurancePhoneFieldToParagraph &&
time drush codit-batch-operations:run MigrateVamcFacilityMentalHealthPhoneFieldToParagraph 

Validate Old Fields Appear on Node New with Toggle Off:

  • Visit the Flipper Toggle admin page and ensure the FEATURE_TELEPHONE_MIGRATION_V1 toggle is not checked.
  • View a VAMC System Billing and Insurance node in a new tab (you will return to this tab later)
  • Confirm the old phone number is visible
  • Confirm the new phone number is not visible
  • View a Staff Profile in new tab (you will return to this tab later)
  • Confirm the old phone number is visible
  • Confirm the new phone number is not visible
  • View a VAMC Facility in a new tab (you will return to this tab later)
  • Confirm the Mental health old phone number is visible
  • Confirm the new phone number is not visible

Validate Old Fields Appear on Node Edit with Toggle Off:

  • Visit the Flipper Toggle admin page and ensure the FEATURE_TELEPHONE_MIGRATION_V1 toggle is not checked.
  • Edit a VAMC System Billing and Insurance node in a new tab (you will return to this tab later)
  • Confirm the old phone number is visible
  • Confirm the new phone number is not visible
  • Edit a Staff Profile in new tab (you will return to this tab later)
  • Confirm the old phone number is visible
  • Confirm the new phone number is not visible
  • Edit a VAMC Facility in a new tab (you will return to this tab later)
  • Confirm the old Mental health phone number is visible
  • Confirm the new phone number is not visible

Validate Old Fields appear on Node Add Forms with Toggle Off:

  • Visit the create VAMC System Billing and Insurance node page in a new tab (you will return to this tab later)
  • Confirm the old phone number is visible
  • Confirm the new phone number is not visible
  • Visit the create Staff Profile node page in a new tab (you will return to this tab later)
  • Confirm the old phone number is visible
  • Confirm the new phone number is not visible
  • Visit the create VAMC Facility node page in a new tab (you will return to this tab later)
  • Confirm the old Mental health phone number is visible
  • Confirm the new phone number is not visible

Validate New Fields Appear on Node View With Toggle On

  • Visit the Flipper Toggle admin page and check the FEATURE_TELEPHONE_MIGRATION_V1 checkbox and save the form.
  • Clear the cache
  • View the VAMC System Billing and Insurance node
  • Confirm the new phone number is visible
  • Confirm the old phone number not visible
  • View the Staff Profile
  • Confirm the new phone number is visible
  • Confirm the old phone number not visible
  • View a VAMC Facility
  • Confirm the new Mental health phone number is visible
  • Confirm the old phone number not visible

Validate New Fields Appear on Node Edit With Toggle On

  • Visit the Flipper Toggle admin page and check the FEATURE_TELEPHONE_MIGRATION_V1 checkbox and save the form.
  • Return to the VAMC System Billing and Insurance node
  • Confirm the new phone number is visible
  • Confirm the old phone number not visible
  • Return to the Staff Profile in new tab
  • Confirm the new phone number is visible
  • Confirm the old phone number not visible
  • Return to the VAMC Facility
  • Confirm the new Mental health phone number is visible
  • Confirm the old Mental health phone number not visible

Validate New Fields appear on Node Add Forms with Toggle On:

  • Visit the create VAMC System Billing and Insurance node page in a new tab (you will return to this tab later)
  • Confirm the old phone number is visible
  • Confirm the new phone number is not visible
  • Visit the create Staff Profile node page in a new tab (you will return to this tab later)
  • Confirm the old phone number is visible
  • Confirm the new phone number is not visible
  • Visit the create VAMC Facility node page in a new tab (you will return to this tab later)
  • Confirm the old Mental health phone number is visible
  • Confirm the new phone number is not visible

Definition of Done

  • Documentation has been updated, if applicable.
  • Tests have been added if necessary.
  • Automated tests have passed.
  • Code Quality Tests have passed.
  • Acceptance Criteria in related issue are met.
  • Manual Code Review Approved.
  • If there are field changes, front end output has been thoroughly checked.

Select Team for PR review

  • CMS Team
  • Public websites
  • Facilities
  • User support
  • Accelerated Publishing

@dsasser dsasser requested a review from a team as a code owner October 9, 2024 20:36
@va-cms-bot va-cms-bot temporarily deployed to Tugboat October 9, 2024 20:36 Destroyed
@github-actions github-actions bot added the Facilities Facilities products (VAMC, Vet Center, etc) label Oct 9, 2024
@va-cms-bot va-cms-bot temporarily deployed to Tugboat October 10, 2024 08:52 Destroyed
@va-cms-bot va-cms-bot temporarily deployed to Tugboat October 10, 2024 18:00 Destroyed
* VACMS-18163: BenefitTaxonomy four configs for how to apply

* VACMS-18163: Added- revision_log_message to group_va_benefit_workflow

* VACMS-18163: changes to config for field translation

* VACMS-18163: Manual addition of - revision_log_message
@omahane
Copy link
Contributor

omahane commented Oct 10, 2024

Post-migration (toggle off)

As soon as I went to look at the node on the node:view (as opposed to node:edit), I noticed that the new field is showing even with the toggle off.

I believe that we would expect to find the old field showing on both the view and edit screens.

Screenshot 2024-10-10 at 4 06 03 PM

Pre-migration (toggle off)

Screenshot 2024-10-10 at 4 28 29 PM

Bumps [va-gov/content-build](https://github.com/department-of-veterans-affairs/content-build) from 0.0.3611 to 0.0.3612.
- [Release notes](https://github.com/department-of-veterans-affairs/content-build/releases)
- [Commits](department-of-veterans-affairs/content-build@v0.0.3611...v0.0.3612)

---
updated-dependencies:
- dependency-name: va-gov/content-build
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
@va-cms-bot va-cms-bot temporarily deployed to Tugboat October 11, 2024 08:53 Destroyed
@omahane
Copy link
Contributor

omahane commented Oct 11, 2024

Node:edit (Toggle on), as content admin

I refactored the form display a bit to account for the fact that we have 2 phone fields on the VAMC facility, as I saw that we ended up hiding the facility phone number on the form for content admins (and above) unintentionally:
Screenshot 2024-10-11 at 10 33 02 AM (2)

@omahane
Copy link
Contributor

omahane commented Oct 11, 2024

We should check

  • node:view for all three content types
  • admins
  • non-admins

@va-cms-bot va-cms-bot temporarily deployed to Tugboat October 11, 2024 20:18 Destroyed
@omahane
Copy link
Contributor

omahane commented Oct 14, 2024

Found a change needed on node:add for VAMC Facility:

  • both the old and new fields are showing
    Screenshot 2024-10-14 at 8 46 04 AM

@va-cms-bot va-cms-bot temporarily deployed to Tugboat October 14, 2024 14:30 Destroyed
@va-cms-bot va-cms-bot temporarily deployed to Tugboat October 14, 2024 16:01 Destroyed
@va-cms-bot va-cms-bot temporarily deployed to Tugboat January 8, 2025 08:33 Destroyed
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)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants