Closed stefaniefgray closed 1 year ago
@jilladams @Dottisea Another one ready to go! 🚀
See linked ticket: https://github.com/department-of-veterans-affairs/va.gov-cms/issues/14588
@stefaniefgray @TroyA6 The redirect was deployed on Wed, Aug 16, which means that this ticket only requires notifying the editor before it can be closed.
Editor notified -- closing
Facility is still flagged as awaiting CSV per @omahane
Redirect ticket: https://github.com/department-of-veterans-affairs/va.gov-cms/issues/14588
Intake
[x] What triggered this runbook? (Flag in CMS, Help desk ticket, Product team, VHA Digital Media) Trigger: Reported on Flagged Facilities view
[x] Link to associated help desk ticket (if applicable) Help desk ticket: https://va-gov.atlassian.net/browse/VAHELP-6114
[x] Name of submitter (if applicable) Submitter: @stefaniefgray
[x] If the submitter is an editor, send them link to KB article: "How Do I Update My VAMC Facility's Basic Location Data?". Let them know that once VAST/Lighthouse has been updated 1/ the Facility Name will be automatically updated and 2/ we will use a Facility name change flag to update the facility's URL. We can notify them once we have been notified that VAST/Lighthouse has been updated.
[x] Link to facility in production: Facility CMS link: https://prod.cms.va.gov/san-francisco-health-care/locations/south-santa-rosa-va-clinic Facility API ID: vha_662GA
Acceptance criteria
VAMC Facility name change
CMS help desk steps
Note: If the help desk is waiting on information from the facility staff or editor, add the "Awaiting editor" flag to the facility with a log message that includes a link to this ticket. Remove the flag when the ticket is ready to be worked by the Facilities team. Be sure to preserve the current moderation state of the node when adding or removing the flag. What happens: The name change is made in VAST, that syncs to Lighthouse which syncs to Drupal.
https://github.com/department-of-veterans-affairs/va.gov-cms/issues/14588
CMS Engineer steps
(Redirects deploy weekly on Wed. at 10am ET, or by requesting OOB deploy (of the revproxy job to prod) in #vfs-platform-support. Coordinate the following items below and canonical URL change after URL change ticket is merged, deployed, and verified in prod.)
Drupal Admin steps (CMS Engineer or Help desk)
Help desk will complete these steps or escalate to request help from CMS engineering.
Changed name
then save node (with moderation state = published)~ The "⏳ Awaiting Redirect" has been removed. The "Changed name" will be retained until we have the CSV changed. But the ticket can be closed, regardless.CMS Help desk (wrap up)