Repository navigation
ER: Issues to examine new wins data will be posted to the old project board #7594
Description
Activity
- moved this to New Issue Approval in P: HfLA Website: Project Board
on Oct 15, 2024 14 remaining items
Hi @castillios, thank you for taking up this issue! Hfla appreciates you :)
Do let fellow developers know about your:-
i. Availability: (When are you available to work on the issue/answer questions other programmers might have about your issue?)
ii. ETA: (When do you expect this issue to be completed?)You're awesome!
P.S. - You may not take up another issue until this issue gets merged (or closed). Thanks again :)
Availability: Weekdays after 6PM
ETA: Tuesday 6/30 by EODIs there a way to locally test pushing Wins as an issue (i.e. local testing within our website forks, similar to how GHA can be tested locally)? I'm curious as I'd like to get an idea of how
function addIssueToProjectBoardColumn(issueID, columnID)should be updated in order to ensure Wins are posted to the new project board.@castillios following up on what we discussed at the meeting, you can take a look at the Apps Script Development Guide and the Admin Guide for an overview of how the Wins page works and how we make changes to the Apps Scripts. I'm also sharing the scripts with the Google account you provided, you will be able to view the originals to look at the functions that may need to be changed, or follow the instructions in the Development Guide to make copies in your own Drive if you'd like to try changing anything.
I also have some more info on how to use GraphQL and some example functions that I will dig up and share with you, but it's been a while since I wrote them so I have to make sure they still work.
Reacted by Maleah Smith- moved this from ERs and epics that are ready to be turned into issues to In progress (actively working) in P: HfLA Website: Project Board
on Jun 28, 2026 @daras-cu Hello! I wanted clarification on how Wins issues are moved to particular columns. In the Wins Form Admin Guide under
createIssue(), it mentions that Win issues will be moved to "New Issue Approval", however in the current code the issue status is set to "In Review". For the issue, should I mention that it should be set to the "New Issue Approval" status field or keep it as is?I'd also like to work on this issue once it's been approved and prioritized!
@castillios as discussed, the issues should go to "Questions/In Review". I just updated the Admin Guide to reflect that.
- moved this from In progress (actively working) to Questions / In Review in P: HfLA Website: Project Board
on Jul 1, 2026 @castillios #8701 looks good, I'm going to close this ER and assign you to that issue. Thanks for all the work you've done so far!
Reacted by Maleah Smith- moved this from Questions / In Review to QA in P: HfLA Website: Project Board
on Jul 11, 2026
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
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
Potential solutions [draft]
need to update the function
function addIssueToProjectBoardColumn(issueID, columnID)in the scriptgh-requestsso that it starts adding the issue to the new project board and it adds it to theReady for PrioritizationcolumnResources:
Instructions for Merge Team