department-of-veterans-affairs / va.gov-cms

Editor-centered management for Veteran-centered content.
https://prod.cms.va.gov
GNU General Public License v2.0
99 stars 68 forks source link

Discovery for enforcing proper workflow for new Facility pages and services #11778

Closed dsinla closed 1 year ago

dsinla commented 1 year ago

Description

The Support team has experienced multiple instances of editors publishing a new Facility page prematurely (sometimes without listing a single service) in a failure to follow the prescribed process. Per the current process, editors are supposed to save pages as DRAFT first, and then notify the Support team.

How can we best implement some guardrails in the CMS to prevent this from happening?

Slack thread

How do I add a facility KB

Related(duplicate?) ticket: https://github.com/department-of-veterans-affairs/va.gov-cms/issues/11481

Acceptance Criteria

CMS Team

Please check the team(s) that will do this work.

stefaniefgray commented 1 year ago

@swirtSJW @davidmpickett Similar inquiry as in #11481 --

Is there a newer/duplicate/alternate version of this ticket with regards to blocking VAMC editors from prematurely publishing new facility homepages in the CMS? (This ticket's title is also pretty fuzzy when we have the specific task nailed down.)

Would like to close in favor of other ticket(s) or consolidate

cc: @JayDarnell @omahane

stefaniefgray commented 1 year ago

@kmariepat-cityfriends Hi! This is the one where we don't want editors publishing new facilities too early without any VAMC Facility Health Services added, i.e. https://github.com/department-of-veterans-affairs/va.gov-cms/issues/12000

davidmpickett commented 1 year ago

I think we can close this specific ticket in favor of https://github.com/department-of-veterans-affairs/va.gov-cms/issues/12911#issuecomment-1541267890

I have done discovery around the problem and proposed a solution over there