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.

Sign up for GitHub

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

Jump to bottom

ER: Add analytics about how many people we reach to the Dashboard #4537

Open
1 of 9 tasks
JessicaLucindaCheng opened this issue Apr 17, 2023 · 5 comments
Open
1 of 9 tasks

ER: Add analytics about how many people we reach to the Dashboard #4537

JessicaLucindaCheng opened this issue Apr 17, 2023 · 5 comments
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
05. Know HFLA

Comments

@JessicaLucindaCheng
Copy link
Member

JessicaLucindaCheng commented Apr 17, 2023 •
edited
Loading

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

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

  • Make a new issue
  • Discuss with team
  • Let a Team Lead know

Potential solutions [draft]

  • Write an issue so that a data analyst or developer can implement adding Google Analytics about how many people we reach/visit the site on https://www.hackforla.org/dashboard/. The issue should include

    • Info that the chart format should be a line chart showing changes over time.

      • After clicking the "Website: General" in the menu, you will be on the "Website Performance: General" page of the dashboard. The line chart should be below the header "Website Performance: General" and above the current two pie charts.
        Click here to see where the line chart should go where-line-chart-goes

    • 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.

      • A last action item for a lead to remove the developer's access to the shared page once the developer (who took on the issue) completes 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.
@JessicaLucindaCheng 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 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
@Josiah-O Josiah-O mentioned this issue May 7, 2023
Closed
4 tasks
@ExperimentsInHonesty ExperimentsInHonesty added this to the 05. Know HFLA milestone May 7, 2023
@ExperimentsInHonesty ExperimentsInHonesty added the Complexity: See issue making label See the Issue Making label to understand the issue writing difficulty level label Oct 10, 2023
@ExperimentsInHonesty ExperimentsInHonesty added the ER Emergent Request label Oct 22, 2023
@JessicaLucindaCheng

This comment was marked as resolved.

Sign in to view
@JessicaLucindaCheng 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
@JessicaLucindaCheng JessicaLucindaCheng mentioned this issue Oct 23, 2023
Closed
2 tasks
@ExperimentsInHonesty

This comment was marked as resolved.

Sign in to view
@ExperimentsInHonesty ExperimentsInHonesty added the ready for dev lead Issues that tech leads or merge team members need to follow up on label Nov 8, 2023
@ExperimentsInHonesty

This comment was marked as resolved.

Sign in to view
@ExperimentsInHonesty
Copy link
Member

The issue will need to instruct the person who takes it on, to get access to
webadmin@hackforla.org
via the website-data-science 1password vault

@ExperimentsInHonesty ExperimentsInHonesty removed the ready for dev lead Issues that tech leads or merge team members need to follow up on label Nov 14, 2023
@JessicaLucindaCheng JessicaLucindaCheng mentioned this issue Jan 21, 2024
Closed
16 tasks
@JessicaLucindaCheng 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 JessicaLucindaCheng added the role: back end/devOps Tasks for back-end developers label Feb 7, 2024
@JessicaLucindaCheng JessicaLucindaCheng removed role: front end Tasks for front end developers role: back end/devOps Tasks for back-end developers labels Feb 13, 2024
@kellyc9 kellyc9 mentioned this issue Apr 9, 2024
Open
16 tasks
@ExperimentsInHonesty ExperimentsInHonesty mentioned this issue Jun 6, 2024
Open
23 tasks
@ExperimentsInHonesty ExperimentsInHonesty moved this to ERs and epics that are ready to be turned into issues in P: HfLA Website: Project Board Jun 23, 2024
@Samhitha444
Copy link
Member

Samhitha444 commented Sep 12, 2024 •
edited by Eleftherios01
Loading

@Eleftherios01 Eleftherios01 mentioned this issue Oct 6, 2024
Open
6 tasks
Open
7 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
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
Projects
P: HfLA Dashboards: Project Board
Status: New Issue Approval
P: HfLA Website: Project Board
Status: ERs and epics that are ready to be turned into issues
Milestone
05. Know HFLA
Development

No branches or pull requests
3 participants
@JessicaLucindaCheng @ExperimentsInHonesty @Samhitha444