Skip to content
d3 Wiki
03.07

Issues, labels, and project boards

Work is visible and prioritized in one place.

Updated
Oct 3, 2026
On this page

Purpose

Work is visible and prioritized in one place.

The standard

  • One org-level project board [TEAM: name] with columns: Intake → Scoped → Ready → In progress → In review → Done.

  • Every issue has: a type: label (bug, feature, chore, question), an area: label (web, rhino, revit, data, infra), and a priority (p0 blocking · p1 this sprint · p2 next · p3 someday).

  • good-first-issue for onboarding tasks.

  • Issue templates: bug (steps, expected, actual, version, screenshots) and feature (problem, proposal, users).

  • Issues are closed by PRs (Closes #123) or explicitly with a reason.

Anti-patterns

Issues with no labels; tasks tracked only in chat; boards nobody looks at (review it in the weekly triage, 01.01).

Owner: [TEAM] · Last reviewed: 2026-09