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 the Tools data to the Languages/Technologies filters #6150

Closed
4 of 5 tasks
ExperimentsInHonesty opened this issue Jan 24, 2024 · 5 comments
Closed
4 of 5 tasks

ER: Add the Tools data to the Languages/Technologies filters #6150

ExperimentsInHonesty opened this issue Jan 24, 2024 · 5 comments
Assignees
@roslynwythe
Labels
Complexity: Missing Complexity: See issue making label See the Issue Making label to understand the issue writing difficulty level ER Emergent Request P-Feature: Home page https://www.hackforla.org/ P-Feature: Projects page https://www.hackforla.org/projects/ p-feature: Projects-check We use this page to check to make sure that teams are using the Technology section correctly ready for dev lead Issues that tech leads or merge team members need to follow up on role: back end/devOps Tasks for back-end developers role: front end Tasks for front end developers size: 0.25pt Can be done in 0.5 to 1.5 hours time sensitive Needs to be worked on by a particular timeframe
Milestone
03.02 Onboarding ...

Comments

@ExperimentsInHonesty
Copy link
Member

ExperimentsInHonesty commented Jan 24, 2024 •
edited
Loading

Emergent Requirement - Problem

We refactored all the tool data so that we could include it in the Languages/Technologies section, of the projects and homepage, by revising it to be Languages/Technologies/Tools. We didn't add it there yet, and I can't find the issue to do so, so if you are trying to search for UsabilityHub, you won't find it in the languages/Technology section.

Issue you discovered this emergent requirement in

Date discovered

2024-01-24

Did you have to do something temporarily

  • YES
  • NO

Who was involved

@ExperimentsInHonesty

What happens if this is not addressed

People are missing a lot of filter options and projects will keep trying to get us to add that info to technologies or languages.

Tools list

ArcGIS surveys (1) AtlasTI (1) Calendly (2) FigJam (2) Figma (13) GitHub (4) GitHub Wiki (1) Google Analytics (3) Google Calendar (1) Google Colab (1) Google Data Studio (1) Google Docs (7) Google Drive (2) Google Forms (3) Google Mail Merge (1) Google Sheets (5) Google Slides (1) Google Suite (2) HackforLA.org guides (1) Hotjar (1) LinkedIn (1) Miro (2) Mplus (1) Observable (2) Otter.ai (3) Photoshop (1) SPSS (1) Sketch (1) Storybook (1) Style Components (1) UsabilityHub (2) Zeplin (1) Zoom (8) paper prototyping (1) phone calls (1) pnpm (1) video production (1) whiteboard / paper & pencil (1)

Resources

https://www.hackforla.org/projects-check/ (it's separated out on this page by design)
https://www.hackforla.org/projects/
https://www.hackforla.org/

Recommended Action Items

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

Potential solutions [draft]
@ExperimentsInHonesty ExperimentsInHonesty added Feature Missing This label means that the issue needs to be linked to a precise feature label. size: 0.25pt Can be done in 0.5 to 1.5 hours role missing Complexity: Missing labels Jan 24, 2024
Open
2 tasks
@ExperimentsInHonesty ExperimentsInHonesty changed the title ER: Bring back the Tools data to the projects and home page ER: Add the Tools data to the Languages/Technologies filters Jan 24, 2024
@ExperimentsInHonesty ExperimentsInHonesty added role: front end Tasks for front end developers role: back end/devOps Tasks for back-end developers P-Feature: Home page https://www.hackforla.org/ P-Feature: Projects page https://www.hackforla.org/projects/ ready for dev lead Issues that tech leads or merge team members need to follow up on p-feature: Projects-check We use this page to check to make sure that teams are using the Technology section correctly Complexity: See issue making label See the Issue Making label to understand the issue writing difficulty level ER Emergent Request Complexity: Missing and removed Feature Missing This label means that the issue needs to be linked to a precise feature label. role missing Complexity: Missing labels Jan 24, 2024
@ExperimentsInHonesty
Copy link
Member Author

I left complexity missing on here, because I don't know the size of the issues that it will make.

@ExperimentsInHonesty ExperimentsInHonesty added time sensitive Needs to be worked on by a particular timeframe Added to dev/pm agenda labels Jan 24, 2024
@roslynwythe
Copy link
Member

@ExperimentsInHonesty Just to confirm, the projects-check page will remain unchanged (with Technologies, Languages and Tools in separate filter groups) but on the projects page, Tools will be incorporated into Languages/Technologies/Tools.

@ExperimentsInHonesty
Copy link
Member Author

ExperimentsInHonesty commented Jan 30, 2024 •
edited
Loading

@roslynwythe Yes. The purpose of that page, is to be able to easily manually check if something seems categorized, which is why we separate them.

@ExperimentsInHonesty Just to confirm, the projects-check page will remain unchanged (with Technologies, Languages and Tools in separate filter groups) but on the projects page, Tools will be incorporated into Languages/Technologies/Tools.

@roslynwythe roslynwythe self-assigned this Jan 30, 2024
@github-actions GitHub Actions

This comment was marked as outdated.

Sign in to view
@roslynwythe
Copy link
Member

roslynwythe commented Jan 30, 2024 •
edited
Loading

@roslynwythe roslynwythe mentioned this issue Jan 30, 2024
Closed
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@roslynwythe roslynwythe

Labels
Complexity: Missing Complexity: See issue making label See the Issue Making label to understand the issue writing difficulty level ER Emergent Request P-Feature: Home page https://www.hackforla.org/ P-Feature: Projects page https://www.hackforla.org/projects/ p-feature: Projects-check We use this page to check to make sure that teams are using the Technology section correctly ready for dev lead Issues that tech leads or merge team members need to follow up on role: back end/devOps Tasks for back-end developers role: front end Tasks for front end developers size: 0.25pt Can be done in 0.5 to 1.5 hours time sensitive Needs to be worked on by a particular timeframe
Projects
P: HfLA Website: Project Board
Archived in project
Milestone
03.02 Onboarding flow
Development

No branches or pull requests
2 participants
@roslynwythe @ExperimentsInHonesty