-
-
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
Epic: Dashboards planning #6614
Comments
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
As a test with @t-will-gillis
We also noticed that although we have manually run the workflow, it still says Apr 10, 2024, 2:12:06 PM instead of 4:00 PM when we last ran it. Relevant to Issues Dashboard Roadmap
|
It looks like someone has made the label I did notice that if we add a label that is not on the spreadsheet, to an issue then it shows up on the report, but labels that are not on the spreadsheet, are on the repo and not on issues should still show up on the top section. |
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
Go through the Dashboard project roadmap and review the issues links inside the issues for ORG https://github.com/orgs/hackforla/projects/88/views/4 |
A new project board view has been created HfLA Dashboards: Project Board, GitHub Org Repos Analysis |
This comment was marked as resolved.
This comment was marked as resolved.
If you have an issue related to one of your dashboards that has an RP000 type number, look for its corresponding wiki page on this link and include it in your roadmap |
We need to sort out |
There are some resources that are in this repo that would be helpful to all people working on writing api calls for looker dashaboards. Also we probably want to put all our looker dashboard python scripts in this repo so that we don't recreate the same scripts over and over, but that will require a rework of the readme, which right now is specific to the issues dashboard. https://github.com/hackforla/live-dashboard-automation |
Mayank issues tab - Skills |
The Issues' dashboard had this as a goal, and we are thinking (at least for now) of making this a separate dashboard with its own requirements.
Notes: |
Internship looker files. You can access them by logging into internship-ba@hackforla.org |
@mayankt153, @ExperimentsInHonesty, @sofiatajide, @Eleftherios06, @Tusharachada1406, @Samhitha444, @Eleftherios01 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.
If you need help, be sure to either: 1) place your issue in the You are receiving this comment because your last comment was before Tuesday, October 15, 2024 at 12:04 AM PST. |
Overview
We need to identify and start building a roadmap for all the website dashboards, so that we can prioritize, manage and recruit.
Details
There are:
See resources for all the issues we were able to find
Action Items
dashboard
on the target repo, have the specific dashboard labelResources/Instructions
List of Repos involved
Dashboard Summary
new issues.
Dashboard URLs
Project board for all Dashboard Issues
https://github.com/orgs/hackforla/projects/88/views/1
Website
Internship
Data Science
team-analytics
The text was updated successfully, but these errors were encountered: