-
-
Notifications
You must be signed in to change notification settings - Fork 766
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
ER: Add analytics about how many people we reach to the Dashboard #4537
Labels
Complexity: Large
Complexity: See issue making label
See the Issue Making label to understand the issue writing difficulty level
ER
Emergent Request
Issue Making: Level 2
Make issue(s) from an ER or Epic
P-Feature: Dashboard
https://hackforla.org/dashboard
role: data analyst
size: 2pt
Can be done in 7-12 hours
Milestone
Comments
JessicaLucindaCheng
added
role: back end/devOps
Tasks for back-end developers
Complexity: Large
ready for dev lead
Issues that tech leads or merge team members need to follow up on
size: 2pt
Can be done in 7-12 hours
P-Feature: Dashboard
https://hackforla.org/dashboard
Issue Making: Level 2
Make issue(s) from an ER or Epic
labels
Apr 17, 2023
JessicaLucindaCheng
added
ready for dev lead
Issues that tech leads or merge team members need to follow up on
and removed
ready for dev lead
Issues that tech leads or merge team members need to follow up on
labels
Apr 25, 2023
4 tasks
ExperimentsInHonesty
added
the
Complexity: See issue making label
See the Issue Making label to understand the issue writing difficulty level
label
Oct 10, 2023
This comment was marked as resolved.
This comment was marked as resolved.
JessicaLucindaCheng
added
ready for product
and removed
ready for dev lead
Issues that tech leads or merge team members need to follow up on
labels
Oct 23, 2023
2 tasks
This comment was marked as resolved.
This comment was marked as resolved.
ExperimentsInHonesty
added
the
ready for dev lead
Issues that tech leads or merge team members need to follow up on
label
Nov 8, 2023
This comment was marked as resolved.
This comment was marked as resolved.
ExperimentsInHonesty
added
role: data analyst
and removed
ready for product
role: back end/devOps
Tasks for back-end developers
labels
Nov 8, 2023
The issue will need to instruct the person who takes it on, to get access to |
ExperimentsInHonesty
removed
the
ready for dev lead
Issues that tech leads or merge team members need to follow up on
label
Nov 14, 2023
16 tasks
JessicaLucindaCheng
changed the title
ER from TLDL: Add analytics about how many people we reach to the Dashboard
ER: Add analytics about how many people we reach to the Dashboard
Feb 7, 2024
JessicaLucindaCheng
added
Ready for Prioritization
role: front end
Tasks for front end developers
and removed
ready for issue making
labels
Feb 7, 2024
ExperimentsInHonesty
added
ready for issue making
and removed
Ready for Prioritization
ready for issue making
labels
Feb 11, 2024
JessicaLucindaCheng
removed
role: front end
Tasks for front end developers
role: back end/devOps
Tasks for back-end developers
labels
Feb 13, 2024
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Complexity: Large
Complexity: See issue making label
See the Issue Making label to understand the issue writing difficulty level
ER
Emergent Request
Issue Making: Level 2
Make issue(s) from an ER or Epic
P-Feature: Dashboard
https://hackforla.org/dashboard
role: data analyst
size: 2pt
Can be done in 7-12 hours
Note: This issue came from the Task List Dev Leads.
Emergent Requirement - Problem
We need to write an issue to add Google Analytics about how many people we reach / visit the site on to https://www.hackforla.org/dashboard/
Who was involved
@SAUMILDHANKAR
What happens if this is not addressed
Analytics about how many people we reach/visit the site are not on the Dashboard.
Resources
Recommended Action Items
Potential solutions [draft]
Info that the chart format should be a line chart showing changes over time.
Click here to see where the line chart should go
An action item that a lead (i.e. tech lead) will need to login to the Looker Studio account. Then, the lead will need to make a page for the developer implementing the changes and then will have to share the page with the developer, who takes on the issue.
Instruction that the developer who takes it on needs to get access to webadmin@hackforla.org via the website-data-science 1Password vault.
The text was updated successfully, but these errors were encountered: