-
Notifications
You must be signed in to change notification settings - Fork 69
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
Create change management plan for revision log requirement #12173
Comments
Just set the date and let VHA Digital Media know when it happens so that they have the time to CM with editors. |
I am meeting with Blake Scates tomorrow, 2/17 to let him know this is upcoming during Sprint 78. We will provide the updated KB article for editors, however the impact is small. Teamsite required revision logs and this would not be new to those editors that previously worked in the teamsite prior to migration |
Plan:
Emailed JHL, Blake, Justine cc'd Dawn and Dave about this on 2/21. JHL will give her editors a heads up on this, but asked that we also send out an email from the Drupal team on the technical ask. We will email editors before the code merges on 2/28 (unless something comes up that I am unaware of). |
Dave has mentioned to hold off on deploy of code for 2/28, however, the change management plan is complete |
Description
Related to #12157. We must determine what level of change management to implement for this new workflow for
VAMC editorsall editors.Teamsite required revision logs and Vet Center editors are currently required to use revision logs as well.Change management for this newly required workflow could include communication (emails, Teams messages, office hours, etc.) from stakeholder partners, KB articles, etc.
User Story
As a CMS editor subject to a newly required revision long, I would like to have change management around this new workflow.
Acceptance Criteria
CMS Team
Please check the team(s) that will do this work.
Program
Platform CMS Team
Sitewide Crew
⭐️ Sitewide CMS
⭐️ Public Websites
⭐️ Facilities
⭐️ User support
The text was updated successfully, but these errors were encountered: