ER: Issues to examine new wins data will be posted to the old project board

[roslynwythe]

Emergent Requirement - Problem

When updated wins json data is pushed from the Google Apps Script, a new "review" issue is created. That issue will be added to the old Project Board instead of the new new HfLA Website: Project Board

Issue you discovered this emergent requirement in

Date discovered

Did you have to do something temporarily

• YES
• NO

Who was involved

@

What happens if this is not addressed

PMs will not be alerted to the need to review new wins submissions and to set their display fields appropriately so that they will appear on the website

Resources

Recommended Action Items

• Make a new issue
• Discuss with team
• Let a Team Lead know

Potential solutions [draft]

need to update the function function addIssueToProjectBoardColumn(issueID, columnID) in the script gh-requests so that it starts adding the issue to the new project board and it adds it to the Ready for Prioritization column

[github-actions]

Hi @roslynwythe.

Please don't forget to add the proper labels to this issue. Currently, the labels for the following are missing:

• Complexity, Role, Feature

NOTE: Please ignore this comment if you do not have 'write' access to this directory.

To add a label, take a look at Github's documentation here.

Also, don't forget to remove the "missing labels" afterwards.
To remove a label, the process is similar to adding a label, but you select a currently added label to remove it.

After the proper labels are added, the merge team will review the issue and add a "Ready for Prioritization" label once it is ready for prioritization.

Additional Resources:

• Wiki: How to create issues
• Wiki: How to read and interpret labels