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.