Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enhance wins sheets to support selection for homepage randomizer #2505

Open
3 of 23 tasks
Tracked by #4134
macho-catt opened this issue Nov 21, 2021 · 32 comments
Open
3 of 23 tasks
Tracked by #4134

Enhance wins sheets to support selection for homepage randomizer #2505

macho-catt opened this issue Nov 21, 2021 · 32 comments
Assignees
Labels
Added to dev/pm agenda automation for manulal github board maintenance actions that are going to be automated Complexity: Large Draft Issue is still in the process of being created Feature: Google Apps Scripts Automation related to Google Apps Scripts GHA New Project Board compatible This GitHub Action issue does not reference columns and will work with the new board ready for product role: back end/devOps Tasks for back-end developers size: 2pt Can be done in 7-12 hours

Comments

@macho-catt
Copy link
Member

macho-catt commented Nov 21, 2021

Dependency

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-responses so 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:
    • share the Wins Form Admin Guide2 as VIEWER
    • share the Wins-form (Response)3 sheet as VIEWER
    • share the Wins-form4
      • Note to lead: make a copy of Wins-form, including the issue # in the name, then share that copy with the developer as EDITOR.
  • 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 insertLatestFormSubmitIntoReviewSheet runs 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 clasp utility 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.js should 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

  1. Wins Apps Script Development Process

  2. Wins Form Admin Guide 2

  3. Wins-form (Response) Sheet 2

  4. Wins-form 2

@macho-catt macho-catt added role: back end/devOps Tasks for back-end developers Complexity: Large P-Feature: Wins Page https://www.hackforla.org/wins/ automation for manulal github board maintenance actions that are going to be automated Ready for Prioritization labels Nov 21, 2021
@github-actions

This comment was marked as outdated.

@macho-catt macho-catt added Feature: Google Apps Scripts Automation related to Google Apps Scripts and removed P-Feature: Wins Page https://www.hackforla.org/wins/ labels Nov 21, 2021
@SAUMILDHANKAR SAUMILDHANKAR self-assigned this Dec 26, 2021
@SAUMILDHANKAR

This comment was marked as outdated.

@github-actions github-actions bot added the Status: Updated No blockers and update is ready for review label Dec 31, 2021
@github-actions github-actions bot added 2 weeks inactive An issue that has not been updated by an assignee for two weeks and removed Status: Updated No blockers and update is ready for review labels Jan 7, 2022
@github-actions

This comment was marked as outdated.

@SAUMILDHANKAR SAUMILDHANKAR removed the 2 weeks inactive An issue that has not been updated by an assignee for two weeks label Jan 7, 2022
@SAUMILDHANKAR

This comment was marked as outdated.

@github-actions github-actions bot added the Status: Updated No blockers and update is ready for review label Jan 14, 2022
@SAUMILDHANKAR

This comment was marked as outdated.

@github-actions github-actions bot removed the Status: Updated No blockers and update is ready for review label Jan 28, 2022
@github-actions

This comment was marked as outdated.

@github-actions github-actions bot added the 2 weeks inactive An issue that has not been updated by an assignee for two weeks label Jan 28, 2022
@SAUMILDHANKAR

This comment was marked as outdated.

@SAUMILDHANKAR SAUMILDHANKAR removed the 2 weeks inactive An issue that has not been updated by an assignee for two weeks label Jan 31, 2022
@github-actions github-actions bot added the Status: Updated No blockers and update is ready for review label Feb 4, 2022
@SAUMILDHANKAR

This comment was marked as outdated.

@github-actions github-actions bot removed the Status: Updated No blockers and update is ready for review label Feb 18, 2022

This comment was marked as outdated.

@roslynwythe roslynwythe added Ready for Prioritization and removed Draft Issue is still in the process of being created ready for dev lead Issues that tech leads or merge team members need to follow up on labels Mar 27, 2024
@ExperimentsInHonesty

This comment was marked as resolved.

@ExperimentsInHonesty ExperimentsInHonesty added ready for dev lead Issues that tech leads or merge team members need to follow up on and removed Ready for Prioritization labels Mar 28, 2024
@roslynwythe roslynwythe added ready for product Added to dev/pm agenda Draft Issue is still in the process of being created and removed ready for dev lead Issues that tech leads or merge team members need to follow up on Added to dev/pm agenda ready for product labels Mar 29, 2024
@roslynwythe

This comment was marked as resolved.

@ExperimentsInHonesty

This comment was marked as resolved.

@ExperimentsInHonesty ExperimentsInHonesty added ready for dev lead Issues that tech leads or merge team members need to follow up on and removed ready for product labels Apr 23, 2024
@roslynwythe

This comment was marked as resolved.

@roslynwythe roslynwythe added ready for product and removed ready for dev lead Issues that tech leads or merge team members need to follow up on labels Jun 17, 2024
@ExperimentsInHonesty ExperimentsInHonesty added the GHA New Project Board compatible This GitHub Action issue does not reference columns and will work with the new board label Jun 18, 2024
@ExperimentsInHonesty
Copy link
Member

RW and I met, and we are going to do the following

  • combine the content on the Homepage summary prototype tab with the Review tab so that there is no risk of the incorrect one being updated.
  • add wins id Google Apps Script: Add unique IDs as object keys for each wins entry #2385
  • create a new tab called Log, which should be manually updated every time a new win is manually added to the homepage randomizer. This way we can see if someone has already been featured and when
  • in the column "# of times appeared on website" it should pull that data from the Log tab by user id
  • add person id
  • create a new tab called person
  • This should have a list of all people and their ids, and the number of wins
    • schema: id, name, email, # of wins ids

@roslynwythe roslynwythe changed the title Google Apps Script: Add automation for Homepage Summary spreadsheet Enhance wins sheets to support selection for homepage randomizer Oct 15, 2024
@roslynwythe
Copy link
Member

@ExperimentsInHonesty the issue has been updated as per your comments in the previous comment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Added to dev/pm agenda automation for manulal github board maintenance actions that are going to be automated Complexity: Large Draft Issue is still in the process of being created Feature: Google Apps Scripts Automation related to Google Apps Scripts GHA New Project Board compatible This GitHub Action issue does not reference columns and will work with the new board ready for product role: back end/devOps Tasks for back-end developers size: 2pt Can be done in 7-12 hours
Projects
Status: New Issue Approval
Development

No branches or pull requests

9 participants