Skip to content

docs: categorize open GitHub issues by complexity and challenge level#1145

Draft
bohandley wants to merge 2 commits intomainfrom
cursor/github-issues-categorization-7bb9
Draft

docs: categorize open GitHub issues by complexity and challenge level#1145
bohandley wants to merge 2 commits intomainfrom
cursor/github-issues-categorization-7bb9

Conversation

@bohandley
Copy link
Contributor

What

Adds docs/github-issues-categorization.md — a comprehensive categorization of all 109 open GitHub issues by coding complexity, challenge level, and work type.

Categories

Category Count Description
Good First Issues 15 Well-scoped tasks ideal for new contributors (a11y fixes, code cleanup, doc updates)
Small Bugs 11 Isolated fixes with clear symptoms, touching 1–3 files
Medium Complexity 25 Multi-file feature work, a11y improvements, chores/refactors
Large / Architectural 16 Framework migrations, performance overhauls, new subsystems
Research Spikes 7 Investigation tasks producing design docs, not production code
Operations / CI / Tooling 13 Deployment automation, dashboards, Slack integrations
Testing Infrastructure 4 E2E test environment and coverage improvements
Epics / Meta 8 Parent/tracking issues (not directly assignable)
Blocked / External 2 Waiting on upstream changes
Cross-Team / Integration 4 Work requiring coordination with other Grafana teams

Why

To help the team prioritize work, onboard new contributors with appropriate "good first issues," and understand the overall shape of the backlog at a glance.

Open in Web Open in Cursor 

…evel

Categories:
- Good First Issues (15): well-scoped a11y fixes, code cleanup, doc updates
- Small Bugs (11): isolated fixes with clear symptoms
- Medium Complexity (25): multi-file features, a11y, chores
- Large/Architectural (16): framework migrations, perf, new subsystems
- Research Spikes (7): investigation tasks, no production code
- Operations/CI/Tooling (13): automation, deployment, dashboards
- Testing Infrastructure (4): E2E test environment and coverage
- Epics/Meta (8): parent/tracking issues
- Blocked/External (2): upstream dependencies
- Cross-Team/Integration (4): multi-team coordination

Co-authored-by: Brendan O'Handley <brendan.ohandley@grafana.com>
@cla-assistant
Copy link

cla-assistant bot commented Mar 18, 2026

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants