Add CMS gh label if/when VFS team selects "unsure" re: CMS question at kickoff

[shiragoodman]

User Story

"As a (persona), I (want to), (so that)."

Assignee: Peer Reviewer:

Description

We have noticed that VFS team have been answering "unsure" to the new, CMS question, "Will a VA editor (Drupal) notice this change?" Instead of recommending the CMS Request touchpoint which could be a waste of time for the VFS, Governance has proposed adding the CMS gh label to the ticket. This would allow the CMS team to review the request, and if they think the VFS teams need to sync with them, then Governance can update the touchpoints. If not, then the CC Request ticket can be left as is, and CMS team will remove their label.

Impacted Artifacts

Live pages

Drafted pages

Tasks

• [ ] Placeholder task

Peer Review

To be completed by peer reviewer

• [ ] User story and acceptance criteria are met

Acceptance Criteria

• [ ] Placeholder AC

Team Notification

• [ ] Slack post on #platform-governance-team
• [ ] Presentation at Weekly Initiative Meeting
• [ ] No notification needed

How to prepare this issue

Refinement

• [ ] Ticket has user story, description, tasks, and acceptance criteria
• [ ] Ticket has been sized
• [ ] Once all above items are checked, add the 'Ready' label.

  Planning

  If this ticket is picked up from the Backlog mid-sprint, connect with Shira to ensure the below items are completed correctly

• [ ] Ticket has been discussed as a team at Planning
• [ ] Ticket has been assigned to appropriate initiative or quarterly epic
• [ ] Ticket has been assigned to a Sprint
• [ ] Ticket has been moved to the Planned pipeline in the Governance team board
• [ ] Ticket as an assignee and peer reviewer

[shiragoodman]

@gracekretschmer-metrostar FYI