Skip to content

Epic: Participant Record Dashboard #7509

Description

@sofiatajide

Overview

We need to manage the work for the participant record dashboard, so that we can prioritize and recruit.

Action Items

  • Go to the participant record tab for the participant record dashboard and copy all of the links in the issue to a comment at the bottom of the issue and indicate whether they are public or private.
  • Copy all of the link lists from the participant record into a comment on this issue
  • Remove duplicates
  • Remove the public private status
  • Review all the links and organize them into the Resources section below
  • Revise Participant Record Dashboard Roadmap

Resources/Instructions

Related issues

Participant Record Dashboard Prototype Links and Notes

Tutorials

The below link is from an issue that had been worked on related to the dashboard. Because we have several dashboards being developed we have organized a list of all tutorials on the Hack for LA Data Science repo wiki, called Dashboard Resources. If you add a new tutorial to any issues related to this dashboard, make sure they get added to the wiki.


Activity

  1. added this to the 08. Team workflow milestone on Sep 23, 2024
  2. self-assigned this
    on Sep 23, 2024
  3. moved this from New Issue Approval to IceBox in P: HfLA Dashboards: Project Boardon Sep 23, 2024
  4. moved this from IceBox to New Issue Approval in P: HfLA Dashboards: Project Boardon Sep 23, 2024
  5. 237 remaining items

  6. sofiatajide commented on Aug 9, 2026

    @sofiatajide
    MemberAuthor
    • Create a new interest form with the following information

        - Name
        - School
        - Practice area drop-down
        - Hours
        - LinkedIn
        - Date for onboarding
      
    • Create a document for the volunteer timeline

  7. sofiatajide commented on Aug 16, 2026

    @sofiatajide
    MemberAuthor
    Instructions
    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 (if necessary): "Add any pictures that will help illustrate what you are working on."
    1. Progress:
      Worked on this Comment
    2. Blockers: None
    3. Availability: at least 6hrs
    4. ETA: n/a
    5. Pictures (if necessary):
  8. hfla-graphql-app commented on Aug 28, 2026

    @hfla-graphql-app
  9. added
    status: 2 Weeks InactiveAn issue that has not been updated by an assignee for two weeks
    and removed on Sep 4, 2026
  10. hfla-graphql-app commented on Sep 4, 2026

    @hfla-graphql-app
  11. hfla-graphql-app commented on Sep 18, 2026

    @hfla-graphql-app
  12. hfla-graphql-app commented on Sep 25, 2026

    @hfla-graphql-app
  13. hfla-graphql-app commented on Oct 2, 2026

    @hfla-graphql-app

    Hello @sofiatajide-

    Please add an update using the below template (even if you have a pull request). Afterwards, remove
    the status: 2 Weeks Inactive label and add the status: Updated label.

    1. Progress: What is the current status of this issue? What have you completed and what is left to do?
    2. Blockers: Explain any 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" status-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 team's hfla-site Slack 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 update was before 09/18/2026, 12:07 AM PDT PST.

  14. hfla-graphql-app commented on Oct 9, 2026

    @hfla-graphql-app

    Hello @sofiatajide-

    Please add an update using the below template (even if you have a pull request). Afterwards, remove
    the status: 2 Weeks Inactive label and add the status: Updated label.

    1. Progress: What is the current status of this issue? What have you completed and what is left to do?
    2. Blockers: Explain any 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" status-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 team's hfla-site Slack 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 update was before 09/25/2026, 12:11 AM PDT PST.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

Relationships

None yet

Development

No branches or pull requests

Issue actions