Requirements for the Issues Dashboard

[amen-ikamba]

Overview

We need to identify and list out the requirements for the Issue dashboard in order to facilitate the work for a developer.

Action Items

• Review existing dashboard requirements and roadmap.
• Audit current project board and remove duplicate or outdated issues.
• Consolidate issue tracking links and ensure alignment with roadmap.
• Update the Issue Dashboard Roadmap with new priorities.
• Review automation processes (GitHub Actions) and update if necessary.
• Conduct final review and gather feedback from stakeholders.

Requirements

• The dashboard should provide clear visibility into key issues and progress.
• Automated updates via GitHub Actions to keep issue statuses current.
• Issues should be categorized by priority and dependencies.
• Labeling system must be consistent and aligned with team workflow.
• Roadmap must reflect ongoing and upcoming tasks with clear deadlines.
• The dashboard should integrate data from GitHub API, and Google Sheets into Looker Dashboards.

Resources/Instructions

• Project Board: HfLA Dashboards
• Documentation: HfLA Wiki - Dashboard

Dashboard Prototype Links and Notes

• V2
  • Looker Dashboard: Dashboard Overview
• V1
  Weekly Label Check #2698
  • GitHub website repo, issue tab, with filter: is:open is:issue label:"ready for dev lead"

Requirements

• Spreadsheet Dashboard - Issues - Competitive or Comparative Analysis Template
• Example roadmap document from another dashboard: HfLA website: Dashboard Requirements: Participant Record v3
  

[github-actions]

Hi @amen-ikamba.

Please don't forget to add the proper labels to this issue. Currently, the labels for the following are missing:

• Complexity, Role, Feature, Size

NOTE: Please ignore this 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.
To remove a label, the process is similar to adding a label, but you select a currently added label to remove it.

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:

• Wiki: How to create issues
• Wiki: How to read and interpret labels