In one line
GitHub introduced Issues in 2009, putting work tracking right next to the code.
This chapter tours the collaboration tools around your code: Issues, Discussions, Projects.
Issues & Sub-issues
Issues are the unit for tracking bugs, tasks, and requests one at a time. Sub-issues break a big effort apart and make parent/child progress visible.
| Feature | What it does | Why it’s good |
|---|---|---|
| 🐛 Issue | Track one task | Labels, assignee, due date |
| 🧩 Sub-issue | Split a parent | Progress bar shows % done |
| 📝 Templates | Structured intake via forms | Nothing gets missed |
| 🔗 Linking | Closes #123 in a PR | Issue auto-closes on merge |
| 🤖 Assign Copilot | Hand an Issue to the agent | Opens a PR for you |
💡 Real examples: VS Code ↗ · Rust ↗ · Next.js ↗ · GitHub Docs ↗
Issue Fields (NEW)
Structured, typed metadata on issues. Generally available as of 2026-07-02. Every organization gets four default fields out of the box (Priority, Effort, Start date, Target date), so priority, effort, and dates stay searchable, reportable, and consistent across every repository.
| Field | Type | Default on | Use |
|---|---|---|---|
| 🔺 Priority | Single select | All types | Shared priority vocabulary |
| ⏱️ Effort | Number / select | Bug / Task / Feature | Estimates & effort |
| 📅 Start / Target date | Date | Feature only | Start & deadline |
| 🛠️ Custom | Any | — | Org-specific values |
⚙️ Setup: org admins add, customize, and choose which fields appear per issue type from Settings › Planning › Issue fields. Managing issue fields ↗
Discussions
A space for “no single right answer” conversations: questions, ideas, announcements. If Issues track tasks, Discussions are where you talk.
- 💬 Q&A format lets you mark a best answer
- 📣 Ideal for release and direction announcements
- 🗳️ Polls gather team opinion fast
- 🔄 Promote a settled thread into an Issue
💡 Real example: GitHub Community ↗ — GitHub itself runs on Discussions.
Project Planning
Projects is a planning tool: spreadsheet, board, and roadmap views over Issues and PRs.
- 📋 Table / Board / Roadmap views
- 🏷️ Custom fields (priority, estimate, due date)
- 🤖 Workflows auto-update status
- 📊 Insights chart your progress
💡 Real example: Vite Team Board ↗ (an OSS project managing work in a public Project).
★ Killer use case
The continuum from conversation to plan to implementation is the real strength.
| Stage | Tool |
|---|---|
| 💬 Discuss | Discussions |
| 🧩 Decompose | Issue + Sub-issues |
| 📋 Plan | Projects |
| 🚀 Build | PR (auto-linked to Issue) |
🎯 Everything inside GitHub = zero tool round-trips. That’s the core of team velocity.