-
-
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
Create Project Board Looker Dashboard for Different Roles #4921
Comments
Hi @kimberlytanyh. Please don't forget to add the proper labels to this issue. Currently, the labels for the following are missing: NOTE: Please ignore the adding proper labels comment if you do not have 'write' access to this directory. To add a label, take a look at Github's documentation here. Also, don't forget to remove the "missing labels" afterwards. After the proper labels are added, the merge team will review the issue and add a "Ready for Prioritization" label once it is ready for prioritization. Additional Resources: |
Weekly Update: Progress:
Blockers: None |
Weekly Update: Progress:
Blockers: None |
@kimberlytanyh
|
NEVERMIND, I ran it again and it cleared everything. |
I'm glad that everything is resolved. I noticed that sometimes there is a lag between changes on the GitHub interface and the results pulled by the API. The same applies to Looker. Sometimes a manual refresh via the "View" menu or reconnecting the connection between the spreadsheet and Looker is necessary to force it to update - scenarios that require these seem to be if you want Looker to refresh data earlier than 15 minutes before its last refresh (because Looker is currently set to refresh data every 15 mins, the earliest setting) or if changes are made to the structure of the dataset in the source spreadsheet (addition of new columns). |
Updates: Progress: Other tasks:
Blockers: Might need to message Sophia as next step to understand the best approach to employing the usage of env files for handoff. Availability: Rest of 11/8, 10AM-6PM for 11/9, and maybe 11/11. ETA: By end of this week or next week. |
@kimberlytanyh It looks like there are only 41 On this page of the dashboard. https://lookerstudio.google.com/u/0/reporting/f42df1c1-99df-4fa1-b719-7e135168bfa3/page/e1JSB |
Hi @djbradleyii, thank you for checking the accuracy of the dashboard and alerting me of your findings. While I have yet to finish completing a comprehensive manual check of the accuracy of the datasets created by my code, I just briefly took a look into the problem you have raised and have the following findings:
However, I do find it intriguing why there is a discrepancy in the link you provided. Perhaps there are also closed issues in the project board? I will do a deeper investigation in the next few days. Thank you so much! |
Weekly Update: Progress:
Next Steps:
Blockers: None |
@ExperimentsInHonesty I have made changes to the script for the dashboard to eliminate running errors and have made the script more concise. The dashboard should be usable again now. Sorry for the inconvenience and delay in rectifying the issue! |
Overview
We are creating a Looker dashboard (that updates on schedule or on-demand) that displays 1) the breakdown of counts of issues by complexity type and role labels per project board columns of interest, 2) the number of issues with a certain status label (e.g. drafts, 2 weeks inactive, etc.) or unknown status by project board columns, and 3) a comprehensive anomaly report to allow developers and other roles access to real-time data to guide issue-making decisions and detect inconsistencies with regular practice.
Action Items
- Developer dashboard with project board column and role breakdown,
- Customer dashboard with column and role breakdown, and
- Anomaly reports broken down into 4 pages:
- Complexity Labeling Anomalies,
- Issues with Missing or No Labels from complexity, role, feature, size, and dependency series,
- Issues with Unofficial Labels, and
- Detecting Blank Issues
(more functionalities to be added by other data scientists/analysts that will take over)
Resources/Instructions
Refer to main issue #4152
The text was updated successfully, but these errors were encountered: