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

Google Data Studio related error on Dashboard page #2776

Closed
7 tasks done
SAUMILDHANKAR opened this issue Feb 13, 2022 · 14 comments
Closed
7 tasks done

Google Data Studio related error on Dashboard page #2776

SAUMILDHANKAR opened this issue Feb 13, 2022 · 14 comments
Assignees
Labels
Complexity: Large P-Feature: Dashboard https://hackforla.org/dashboard role: back end/devOps Tasks for back-end developers size: 2pt Can be done in 7-12 hours
Milestone

Comments

@SAUMILDHANKAR
Copy link
Member

SAUMILDHANKAR commented Feb 13, 2022

Overview

As a developer, I want to make sure that up-to-date data is reflected on the Dashboard page. For this issue, we will fix the error where data related to remote onboarding is not visible on the dashboard page.

Action Items

  • Request Google data studio access from tech leads/merge team
  • Review how the data set is configured (Remote Onboarding data tab)
  • Identify the reasons for the error and explore ways to fix it
  • If required, make a copy of the Survey Data Workbook in your drive to test the changes in your own repo
  • Please upload the screenshots from your repo once the error is fixed
  • Discuss your solution with the tech leads or in a team meeting (before making final configuration changes)
  • Make sure no other functionality is impacted, once the error is fixed

Resources/Instructions

Screenshot of the error page

Dashboard page error

Data set configuration error log

Data set configuration error log

Google data studio error page
Dashboard page
Survey Data Workbook
Remote Onboarding data tab

@SAUMILDHANKAR SAUMILDHANKAR added role: back end/devOps Tasks for back-end developers Complexity: Large size: 2pt Can be done in 7-12 hours P-Feature: Dashboard https://hackforla.org/dashboard labels Feb 13, 2022
@github-actions

This comment was marked as resolved.

@SAUMILDHANKAR SAUMILDHANKAR changed the title Draft: Fix error on Dashboard page Fix error on Dashboard page Mar 10, 2022
@ExperimentsInHonesty

This comment was marked as outdated.

@SAUMILDHANKAR SAUMILDHANKAR changed the title Fix error on Dashboard page Google Data Studio related error on Dashboard page Apr 5, 2022
@ExperimentsInHonesty ExperimentsInHonesty added this to the 05. Know HFLA milestone Apr 6, 2022
@jdingeman jdingeman self-assigned this Aug 19, 2022
@github-actions
Copy link

Hi @jdingeman, thank you for taking up this issue! Hfla appreciates you :)

Do let fellow developers know about your:-
i. Availability: (When are you available to work on the issue/answer questions other programmers might have about your issue?)
ii. ETA: (When do you expect this issue to be completed?)

You're awesome!

P.S. - You may not take up another issue until this issue gets merged (or closed). Thanks again :)

@jdingeman
Copy link
Member

Availability: Every day after 3pm
ETA: Sunday, August 28 EOD

@jdingeman jdingeman assigned jdingeman and unassigned jdingeman Aug 19, 2022
@hackforla hackforla deleted a comment from github-actions bot Aug 19, 2022
@jdingeman
Copy link
Member

Will begin issue after my medium issue pull request is merged.

@jdingeman
Copy link
Member

When prompted to create a copy of the Google Data Studio environment, I am presented with this issue
image

I am not sure why the data sources are "unknown" but perhaps we can try to fix that. I don't want to try and rename the whole thing and affecting the data that is already transferred into the studio.

But more on the issue, I am not sure what the layout of the Suggestions for Improvement by Respondent should be. After reconnecting that module to a new data source using the Survey Data Workbook | Remote Onboarding, this is how it immediately appeared:
image

I think the only issue with this is that the module needed to be reconnected to the workbook.

@github-actions github-actions bot added the Status: Updated No blockers and update is ready for review label Aug 26, 2022
@github-actions github-actions bot removed the Status: Updated No blockers and update is ready for review label Sep 2, 2022
@github-actions
Copy link

github-actions bot commented Sep 2, 2022

@jdingeman

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the developer meeting discussion column and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel.

You are receiving this comment because your last comment was before Tuesday, August 30, 2022 at 12:27 AM PST.

@github-actions github-actions bot added the 2 weeks inactive An issue that has not been updated by an assignee for two weeks label Sep 2, 2022
@jdingeman
Copy link
Member

UPDATE:
Progress: Unchanged. Need administrative approval for updating data studio.
Blockers: Mentioned in progress.
Availability: Every day after 3pm
ETA: Hopefully by next Monday, 9/12

@jdingeman jdingeman removed the 2 weeks inactive An issue that has not been updated by an assignee for two weeks label Sep 7, 2022
@jdingeman jdingeman added the Status: Updated No blockers and update is ready for review label Sep 7, 2022
@jdingeman
Copy link
Member

Added data source into main data studio.
image

Ready for issue close unless formatting is needed. @kathrynsilvaconway @ExperimentsInHonesty

@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 Sep 16, 2022
@github-actions
Copy link

@jdingeman

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the developer meeting discussion column and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel.

You are receiving this comment because your last comment was before Tuesday, September 13, 2022 at 12:32 AM PST.

@arpitapandya arpitapandya removed the 2 weeks inactive An issue that has not been updated by an assignee for two weeks label Sep 16, 2022
@arpitapandya
Copy link
Member

I had a meeting with @jdingeman on 2022-09-15. We reviewed all the relevant changes and it's correct and working. Also, meets all the issue requirements and a working copy. Great job @jdingeman

@ExperimentsInHonesty
Copy link
Member

product needs to review

@ExperimentsInHonesty
Copy link
Member

Ready for product - we need to review the comments and see what action items are necessary and which suggestions are resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Complexity: Large P-Feature: Dashboard https://hackforla.org/dashboard role: back end/devOps Tasks for back-end developers size: 2pt Can be done in 7-12 hours
Projects
Development

No branches or pull requests

4 participants