-
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
VACMS-9717 Make CMS the source of truth for VAMC mental health phone #15585
Conversation
2575fc3
to
fe8fa5e
Compare
fe8fa5e
to
91ed556
Compare
phone number example as been added. |
5f04bc9
to
32f45be
Compare
Seed data was pushed from my local to LH prod on 12/1/2023 |
This commit was moved to its own PR |
… number (#15468) * VACMS-14213 Move VAMC mental health number to editable region. * VACMS-14213 Remove Mental health phone number from VACMS facility migration. * VAMC-14213 Updated help text. * VACMS-14213 Change phone field labels to title case.
* Revert "VACMS-14213 Make CMS the source of truth for VAMC mental health phone number (#15468)" This reverts commit 2575fc3. in order to restore the field location in the api data and its place in the migration. * VACMS-15647 Add editable mental health contact field to VAMC facility
71f7aec
to
04c1ca2
Compare
Closing to toggle tugboat stuck |
Opening to unstick tugboat |
Closing again because now we have two tugboat instances. |
Re-opening to jumpstart tugboat |
Same failing cypress test. Investigating |
The Cypress failure occurring on this PR is unrelated to Mental health numbers and is failing across multiple PRs. It should not hold up merging this, BUT it will prevent this from going out with today's deploy. |
I am merging this so that it will be ready to go out when the other issue is resolved. |
Description
This is the PR of the integration branch. It can not be merged until LH is prepared to receive.
Relates to #9717 and merging is covered by #15576
This PR is set to merge on Tuesday Jan 16th in time for deploy on that day.
Testing done
Screenshots
QA steps
What needs to be checked to prove this works?
What needs to be checked to prove it didn't break any related things?
What variations of circumstances (users, actions, values) need to be checked?
As user uid with user_role
Definition of Done
Select Team for PR review
CMS Team
Public websites
Facilities
User support
Accelerated Publishing
Is this PR blocked by another PR?
DO NOT MERGE
Does this PR need review from a Product Owner
Needs PO review
CMS user-facing announcement
Is an announcement needed to let editors know of this change?