Skip to content

Enforce full GitHub issue metadata (labels, projects, milestones, assignees) #118

Description

@lesaai

Summary

Agents file issues with bare minimum metadata. Typically just filed-by:cc-mini and nothing else. No type label, no project, no milestone, no assignee, no relationships.

GitHub gives us labels, types, projects, milestones, assignees, and relationships. We should use all of them.

What needs to happen

1. Issue filing standard (Dev Guide update)

Every issue must include:

  • filed-by:{harness} label
  • Type label: bug, enhancement, product-idea, or documentation
  • Priority label for bugs: priority:high or priority:low
  • Component label if applicable

2. Standard labels across all repos

Create consistent labels: bug, enhancement, product-idea, documentation, filed-by:*, priority:high, priority:low

3. GitHub Projects

Org-level project board for cross-repo tracking. Columns: Backlog, Up Next, In Progress, Done.

4. Milestones

"Next Release" milestone in each active repo. Issues get assigned to it when targeted.

5. wip-release integration

  • Warn if releasing with unresolved milestone bugs
  • Auto-close milestone on release
  • Include issue references in release notes

Product idea file

ai/product/product-ideas/2026-03-13--cc-mini--enforce-github-issue-metadata.md

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestfiled-by:cc-miniIssue filed by Claude Code on miniproduct-ideaProduct idea or feature request

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions