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

ER: Create a skills dashboard #4532

Open
2 tasks
JessicaLucindaCheng opened this issue Apr 17, 2023 · 16 comments
Open
2 tasks

ER: Create a skills dashboard #4532

JessicaLucindaCheng opened this issue Apr 17, 2023 · 16 comments
Assignees
Labels
Complexity: Large Draft Issue is still in the process of being created epic ER Emergent Request feature: skills / productivity ladder dashboard Issue Making: Level 5 Make a Rollout Plan that has >1 epics to achieve and timelines for interdependencies ready for org rep role: back end/devOps Tasks for back-end developers role: front end Tasks for front end developers size: 13+pt Must be broken down into smaller issues Status: Help Wanted Internal assistance is required to make progress

Comments

@JessicaLucindaCheng
Copy link
Member

JessicaLucindaCheng commented Apr 17, 2023

Note: This issue came from the Task List Dev Leads.

Emergent Requirement - Problem

Issue Description
As Hack for LA members, we need a skills dashboard so that we can track the skills we have gained at Hack for LA.

Who was involved

What happens if this is not addressed

Members won't have a skills dashboard that allows them to easily track the skills they have gained at Hack for LA.

Resources

Recommended Action Items

  • Requirements elicitation: Discuss with Stakeholder Rep (Bonnie) what is desired for the skills dashboard
  • Write an issue for implementing a skills dashboard and include a blank version of the spreadsheet for use by the website team. (See link to Google Sheet in Resources.)

Potential solutions [draft]

  • It will mainly be an internal product.
  • Skills labels will be added to all the issues
  • Then the looker dashboard will tell leads (and maybe members themselves) what skills have been gained based on completed, closed issues.
@github-actions github-actions bot added Feature Missing This label means that the issue needs to be linked to a precise feature label. role missing labels Apr 17, 2023
@github-actions

This comment has been minimized.

@JessicaLucindaCheng JessicaLucindaCheng changed the title ER from TLDL: ER from TLDL: Create a skills dashboard Apr 17, 2023
@JessicaLucindaCheng JessicaLucindaCheng added role: front end Tasks for front end developers role: back end/devOps Tasks for back-end developers Complexity: Large P-Feature: Dashboard https://hackforla.org/dashboard size: 13+pt Must be broken down into smaller issues epic ready for dev lead Issues that tech leads or merge team members need to follow up on Issue Making: Level 5 Make a Rollout Plan that has >1 epics to achieve and timelines for interdependencies and removed Complexity: Missing P-Feature: Dashboard https://hackforla.org/dashboard 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
@ExperimentsInHonesty ExperimentsInHonesty added this to the 08. Team workflow milestone May 7, 2023
@ExperimentsInHonesty ExperimentsInHonesty added feature: skills / productivity ladder dashboard and removed Feature Missing This label means that the issue needs to be linked to a precise feature label. labels Jul 16, 2023
@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
Copy link
Member Author

JessicaLucindaCheng commented Oct 23, 2023

@ExperimentsInHonesty

  1. Is this the same as Develop Engineering Skills Matrix engineering#65? If yes, should this be closed?
    Answer from Bonnie: No, it's different. We are going to add skills labels to all the issues and then the looker dashboard will tell lead (and maybe members themselves) what skills have been gained. It will be an internal product.

  2. If no,
    i. Should requirements elicitation be an action item in this ER or its resultant issue? See Recommended Action Items.
    ii. Is there anything else that needs to be added to this ER to make it ready for issue making? I wasn't sure what specifics you were thinking of for the skills dashboard.
    Answer for both of these questions from Bonnie: More specifics and details about the requirements for the skills dashboard will be added by org rep.

@JessicaLucindaCheng JessicaLucindaCheng added the ER Emergent Request label Jan 26, 2024
@t-will-gillis

This comment was marked as off-topic.

@JessicaLucindaCheng JessicaLucindaCheng changed the title ER from TLDL: Create a skills dashboard ER: Create a skills dashboard Feb 8, 2024
@ExperimentsInHonesty
Copy link
Member

@t-will-gillis this is not really written up as an issue to work on. I need to do that. I will assign myself to this draft. But please don't remove n2020h from the repo

@ExperimentsInHonesty ExperimentsInHonesty self-assigned this Mar 4, 2024

This comment has been minimized.

@github-actions github-actions bot added the 2 weeks inactive An issue that has not been updated by an assignee for two weeks label May 24, 2024

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

Copy link

@ExperimentsInHonesty, @n2020h

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' 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 Questions/In Review column of the Project Board 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. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

You are receiving this comment because your last comment was before Tuesday, June 11, 2024 at 12:06 AM PST.

@n2020h
Copy link
Member

n2020h commented Jun 17, 2024

Progress: Created GH actions scripting to create csv.
Connected csv to looker dashboard: https://lookerstudio.google.com/reporting/23182581-babc-4907-a534-e38db0ecef3e
Currently attempting to recreate original model dashboard.

Blockers: Unsure about how some of the original data was queried or configured to create original charts and visualizations. I would like to look behind the scenes of original dashboard. Currently I am receiving "Chart configuration incomplete" errors on my dashboard.

Availability: I have 4 hours this week

ETA: Pending response to blocker.

Pictures (optional):
image

@n2020h n2020h pinned this issue Jun 17, 2024
@n2020h n2020h unpinned this issue Jun 17, 2024
@n2020h n2020h added the Status: Help Wanted Internal assistance is required to make progress label Jun 17, 2024
@ExperimentsInHonesty
Copy link
Member

ExperimentsInHonesty commented Jun 18, 2024

@Rabia2219 In order to give @n2020h access to a copy of the skills dashboard, we need to copy IS21: Skill Audit spreadsheet,, desidentify the data in the copy, copy the copy and remove the data that is unneeded, copy that copy, and re-connect the data to the new skills dashboard copy and share with her

Tabs

NEW FORMAT
Matrix
Skills Data

@ExperimentsInHonesty ExperimentsInHonesty removed the 2 weeks inactive An issue that has not been updated by an assignee for two weeks label Jun 18, 2024
@Rabia2219
Copy link
Member

Rabia2219 commented Jun 20, 2024

Update

  • The original skills audit spreadsheet was copied, PII was removed
  • Created a copy again
  • Made a copy of the dashboard and connected the new spreadsheet as the data source
    • each tab for new data source has to be connected first
    • you can remove the original data source
    • each visualization has to be manually connected to the data source (tabs in the data source)
    • the 'Participating Interns' chart wasn't linking properly to the data source, (even though the same data source was working for other visualizations). I replicated the chart and linked it to the related data source and it worked. I then deleted the original chart.

@mayankt153
Copy link
Member

mayankt153 commented Aug 25, 2024

@n2020h We are in the process of reorganizing where we are keeping the assets for skills dashboard. We need to add you to another Google Drive because we moved some items you might have been working on.

Please provide your email address. Nevermind, we found it in the roster.

@mayankt153
Copy link
Member

mayankt153 commented Sep 22, 2024

  • All the links in this issue will need to be checked to see if we have access
  • Task List Dev Leads
    • Have access, its located in ____
    • public
  • Dashboard Drive Folder
    • Have access, its located in HfLA Dashboards -> Skills Dashboard
    • public
  • IS21: Skill Audit
    • I don't have access - located in Internship > Internships > IS21 cohort - brentwood only > Skill Analysis (has PII, and we will need Rabia to make a version and relink it to the current demo so that it's movable to the new dashboard drive)
    • public

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Complexity: Large Draft Issue is still in the process of being created epic ER Emergent Request feature: skills / productivity ladder dashboard Issue Making: Level 5 Make a Rollout Plan that has >1 epics to achieve and timelines for interdependencies ready for org rep role: back end/devOps Tasks for back-end developers role: front end Tasks for front end developers size: 13+pt Must be broken down into smaller issues Status: Help Wanted Internal assistance is required to make progress
Projects
Status: New Issue Approval
Status: Questions / In Review
Development

No branches or pull requests

6 participants