-
-
Notifications
You must be signed in to change notification settings - Fork 776
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
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
Milestone
Comments
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
This comment was marked as outdated.
This comment was marked as outdated.
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
This comment was marked as outdated.
This comment was marked as outdated.
github-actions
bot
added
the
Status: Updated
No blockers and update is ready for review
label
Dec 31, 2021
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
This comment was marked as outdated.
This comment was marked as outdated.
SAUMILDHANKAR
removed
the
2 weeks inactive
An issue that has not been updated by an assignee for two weeks
label
Jan 7, 2022
This comment was marked as outdated.
This comment was marked as outdated.
github-actions
bot
added
the
Status: Updated
No blockers and update is ready for review
label
Jan 14, 2022
This comment was marked as outdated.
This comment was marked as outdated.
github-actions
bot
removed
the
Status: Updated
No blockers and update is ready for review
label
Jan 28, 2022
This comment was marked as outdated.
This comment was marked as outdated.
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
This comment was marked as outdated.
This comment was marked as outdated.
SAUMILDHANKAR
removed
the
2 weeks inactive
An issue that has not been updated by an assignee for two weeks
label
Jan 31, 2022
3 tasks
github-actions
bot
added
the
Status: Updated
No blockers and update is ready for review
label
Feb 4, 2022
This comment was marked as outdated.
This comment was marked as outdated.
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.
This comment was marked as outdated.
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
This comment was marked as resolved.
This comment was marked as resolved.
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
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
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
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
This comment was marked as resolved.
This comment was marked as resolved.
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
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
moved this to New Issue Approval
in P: HfLA Website: Project Board
Jun 23, 2024
RW and I met, and we are going to do the following
|
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
@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
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
wins-form-responses
so all commands should be run from/google-apps-script/wins-form-responses
Wins-form
, including the issue # in the name, then share that copy with the developer as EDITOR.insertLatestFormSubmitIntoReviewSheet
runs when the test form is submitted.clasp
utility can be used to transfer code back and forth between the local worksation and the Google Drive as needed.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()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
Resources/Instructions
Footnotes
Wins Apps Script Development Process ↩
Wins Form Admin Guide ↩ ↩2
Wins-form (Response) Sheet ↩ ↩2
Wins-form ↩ ↩2
The text was updated successfully, but these errors were encountered: