Merge remote-tracking branch 'origin/VACMS-00000-fix-password-issue' …

…into VACMS-00000-fix-password-issue

.github/ISSUE_TEMPLATE/runbook-vet-center-new.md

@@ -52,15 +52,16 @@ Facility API ID: <insert_facility_API_ID>
 **If a Vet Center:**
 - [ ] Become aware that the new facility is now on the Facility API (typically, via a Flag).
 - [ ] Check with Readjustment Counseling Services to (1) confirm what district the Vet Center belongs, (2) identify the Vet Center Director and Outreach Specialist (names/email addresses), (3) confirm the new location isn't a replacement for an existing Outstation
+- [ ] Create a Vet Center - Locations List node for the Vet Center and save as Draft
 - [ ] In [Sections taxonomy](https://prod.cms.va.gov/admin/structure/taxonomy/manage/administration/overview), move the Vet Center Section to the appropriate district.
 - [ ] Create account access as directed by RCS. If editors are new to Drupal, create accounts with editor rights only for Vet Center Director and Outreach Specialist so that they cannot publish on their own.
-- [ ] Contact Vet Center Director and Outreach specialist to onboard for training [@TODO write sample email - SEE runbook-vamc-facility-new] **Note: this should include instructions for adding content and preparing for publishing and RCS Central Office should be included as CC**
+- [ ] Contact Vet Center Director and Outreach specialist to onboard for training [@TODO write sample email - SEE runbook-vamc-facility-new] **Note: this should include instructions for adding content, updating the Locations list, and preparing for publishing and RCS Central Office should be included as CC**
 - [ ] Add flag `Awaiting editor` to this facility. Note: This is now blocked until RCS Central office approves.
 - [ ] **Once approved by RCS Central Office as complete, proceed to Drupal Admin publishing steps**
 
 
 **Drupal Admin steps**
-- [ ] Bulk publish the nodes and facility.
+- [ ] Bulk publish the nodes, Locations list and facility.
 
 #### After next nightly Facilities migration to Lighthouse
 - [ ] Validate that the change has deployed by checking that the Facility Locator has been updated with the new url.

.github/ISSUE_TEMPLATE/runbook-vet-center-outstation-to-vet-center.md

@@ -35,29 +35,30 @@ Facility API ID: <insert_facility_API_ID>
 **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.**
 
 #### Edit new Vet Center
-- [ ] 1. Become aware that the new Vet Center is now in the Facility API and in the CMS (typically, via a Flag, but this may come in as a help desk ticket).
-- [ ] 2. Check with RCS(?) what district it belongs to, or it may be pulled from the former Outstation.
-- [ ] 3. Update the Section (default is "Vet Center", but it should be under a district).
-- [ ] 4.  Communicate with editor (cc VHA Digital Media) to give them go-ahead to complete the content. An Outstation does not have any services, but a Vet Center does, so these must be added.
+- [ ] Become aware that the new Vet Center is now in the Facility API and in the CMS (typically, via a Flag, but this may come in as a help desk ticket).
+- [ ] Check with RCS(?) what district it belongs to, or it may be pulled from the former Outstation.
+- [ ] Update the Section (default is "Vet Center", but it should be under a district).
+- [ ] Create a Vet Center - Locations List node for the Vet Center and save as Draft
+- [ ] Communicate with editor (cc VHA Digital Media) to give them go-ahead to complete the content, including Locations list. An Outstation does not have any services, but a Vet Center does, so these must be added.
 #### Publish new Vet Center
-- [ ] 5. When editor has prepared content and let help desk know, publish the new Vet Center.
-- [ ] 6. Remove the `New facility` flag from the node.
-- [ ] 7. Communicate with editor (do they need to be onboarded)
+- [ ] When editor has prepared content and let help desk know, publish the new Vet Center, and Locations list / Services.
+- [ ] Remove the `New facility` flag from the node.
+- [ ] Communicate with editor (do they need to be onboarded)
 
 #### Close old Outstation and Create Vet Center URL
-- [ ] 8. Create a [URL change request](https://github.com/department-of-veterans-affairs/va.gov-cms/issues/new?assignees=&template=runbook-facility-url-change.md&title=URL+Change+for%3A+%3Cinsert+facility+name%3E), changing the entry from the old facility URL to the new facility URL. (**Note: The URL change request ticket blocks the completion of this ticket.**)
+- [ ] Create a [URL change request](https://github.com/department-of-veterans-affairs/va.gov-cms/issues/new?assignees=&template=runbook-facility-url-change.md&title=URL+Change+for%3A+%3Cinsert+facility+name%3E), changing the entry from the old facility URL to the new facility URL. (**Note: The URL change request ticket blocks the completion of this ticket.**)
 
 <insert_url_change_request_link>
 
 ### CMS engineer steps
-- [ ] 9. Execute the steps of the URL change request ticket from step 8.
+- [ ] Execute the steps of the URL change request ticket from step 8.
 
 (Redirects deploy daily except Friday at 10am ET, or by requesting OOB deploy (of the revproxy job to prod) in #vfs-platform-support. Coordinate the items below and canonical URL change after URL change ticket is merged, deployed, and verified in prod.)
 
 ### Drupal Admin steps
 _Help desk will complete these steps or escalate to request help from CMS engineering._
-- [ ] 10. When the redirect has been made live, set the status of the Outstation node to 'closed'.
-- [ ] 11. Archive the Outstation with a comment in the revision log that points to the new Vet Center.
+- [ ] When the redirect has been made live, set the status of the Outstation node to 'closed'.
+- [ ] Archive the Outstation with a comment in the revision log that points to the new Vet Center.
 
 ### Helpdesk steps
-- [ ] 12. Help desk notifies editor and any other stakeholders.
+- [ ] Help desk notifies editor and any other stakeholders.