-
-
Notifications
You must be signed in to change notification settings - Fork 847
Open
Labels
Added to dev/pm agendaComplexity: LargeDraftIssue is still in the process of being createdIssue is still in the process of being createdFeature: Google Apps ScriptsAutomation related to Google Apps ScriptsAutomation related to Google Apps ScriptsGHA New Project Board compatibleThis GitHub Action issue does not reference columns and will work with the new boardThis GitHub Action issue does not reference columns and will work with the new boardautomationfor manual github board maintenance actions that are going to be automatedfor manual github board maintenance actions that are going to be automatedready for productrole: back end/devOpsTasks for back-end developersTasks for back-end developerssize: 2ptCan be done in 7-12 hoursCan be done in 7-12 hours
Milestone
Description
Dependency
- Google Apps Script: Fix data errors in spreadsheet used for wins page #2901
- Create wiki page "Hfla Google Apps Script Development/Review Process" #4134
- Add latest version of Google Apps Scripts to GitHub #3641
Overview
We need enhancements to Wins-form (Responses) to help PMs in identifying which wins entries should be displayed in the website homepage randomizer.
Action Items
- Follow sections 1-3 in the Wins Apps Script Development Process1. Note that in this issue you will only be modifying the Apps Script
wins-form-responsesso all commands should be run from/google-apps-script/wins-form-responses - As described in section 3a and 3b, you will provide a dev lead with the google account you wish to use for testing, and request the dev lead to:
- Continue following instructions in 3c and d. As described in 3d, you will have to make modifications to certain documents in the test folder.
- Update settings in Wins-form so that responses are stored in your test version of Wins-form (Response)
- In Wins-form (Response), add trigger so that
insertLatestFormSubmitIntoReviewSheetruns when the test form is submitted.
- Continue following instructions through section 6 "Editing". As described in this section, editing can be done locally in an IDE or in the Google Drive cloud editor, and the
clasputility can be used to transfer code back and forth between the local worksation and the Google Drive as needed. - Copy columns H through R from the "Homepage Summary" sheet to the "Review" sheet.
- Create a new sheet "Log". Label the fist column "Wins ID" and copy columns F through H from the "Homepage Summary" sheet to the "Log" sheet, to the right of the "Wins ID" column
- Setup a formula so that column "# of times appeared on website" on the Review sheet, is sourced from the "Log" sheet, based on matching the "Wins ID" columns on the "Review" and "Log" sheets.
- On the Review sheet, add a new column "Person ID" to the right of "Wins ID"
- Create a new tab/sheet "Persons" with columns "Person ID", "email", "# of wins IDs"
- Add code so that when a new wins submission is processed, a "Person ID" is assigned, and the "# of wins IDs" is populated, based on the assumption that each unique email address represents a unique "person".
- Test the code to confirm that both for new form submissions and for Review sheet updates, both the Review, Log, and Persons sheets are updated appropriately.
- You will not have to run
main()for this issue, so if there are errors related to not having access to gh-requests, you can remove the gh-requests library and if necessary "comment out" main() - Follow all steps through section 8 "Completing an issue". For this issue, only a single file
google-apps-script/wins-form-responses/Code.jsshould be committed. Contact the dev lead via Slack to arrange the review.
Merge Team/dev Lead
- ensure that all access to Wins Form Admin Guide2, the Wins-form (Response) Sheet3, and the Wins-form4 have been revoked.
Resources/Instructions
Footnotes
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Added to dev/pm agendaComplexity: LargeDraftIssue is still in the process of being createdIssue is still in the process of being createdFeature: Google Apps ScriptsAutomation related to Google Apps ScriptsAutomation related to Google Apps ScriptsGHA New Project Board compatibleThis GitHub Action issue does not reference columns and will work with the new boardThis GitHub Action issue does not reference columns and will work with the new boardautomationfor manual github board maintenance actions that are going to be automatedfor manual github board maintenance actions that are going to be automatedready for productrole: back end/devOpsTasks for back-end developersTasks for back-end developerssize: 2ptCan be done in 7-12 hoursCan be done in 7-12 hours
Type
Projects
Status
New Issue Approval