Discovery around GH actions auto populate column in GH projects board for PO Sync

[shiragoodman]

User Story

As a Governance team member, I want to be able to easily see in the Collab Cycle Reviews GH Projects board if a VFS team participated in a PO Sync so that I can know if it's ok to move forward with a previously scheduled touchpoint.

Assignee: @it-harrison Peer Reviewer: @KKitagawa-Bosch

Description

Both OCTO-DE Design PA leads and Governance team need to be able to easily see if a VFS team has completed the PO Sync touchpoint. However, since this is an OCTO only touchpoint, Governance will not easily see/know when a PO Sync occurred (like they do with a DI, MPR or SR). OCT-DE Design PA Leads do have an action to add the PO-Sync-approved label to the Collaboration Cycle Request ticket post-PO Sync, however the built-in automations in GitHub projects do not allow for a field to be populated based on whether or not a label exists or not.

The purpose of this ticket is to add a new GH actions script to the Collaboration Cycle Reviews gh projects board that would auto populate a new field in the board to make it easy for all to see that the PO sync occurred and was approved.

Note: Eric Boehs shared a script he wrote with the #github-projects-cop channel that may be helpful. Check it out!

Impacted Artifacts

Live pages

Drafted pages

Tasks

• [ ] After doing initial discovery, contact Shira if there are limitations and/or restrictions to completing this ticket

Peer Review

To be completed by peer reviewer

• [ ] User story and acceptance criteria are met

Acceptance Criteria

• [ ] We had a new column in the Collab Cycle Reviews GH projects board that specifies whether the PO sync occurred and if it was approved.

Team Notification

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

How to prepare this issue

Refinement

• [x] Ticket has user story, description, tasks, and acceptance criteria
• [x] Ticket has been sized
• [x] 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

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

[it-harrison]

I have verified locally that this is doable - I have also added an action to the repo; however, the permissions generated for the GITHUB_TOKEN during the workflow run are not sufficient to modify a project (whereas my personal token is); I am working with support to increase permissions.

[it-harrison]

@KKitagawa-Bosch check out the action and the script the action calls

[shiragoodman]

Due to @it-harrison 's comments above, this work will be moving into the next sprint.