GitHub Issues

Built-in project tracking for development teams

Native issue tracking, project boards, and roadmap views built into GitHub. Includes sub-issues, custom fields, table/board/roadmap views, Copilot-powered issue summaries, and deep integration with pull requests, commits, and actions. No separate product — included with every GitHub plan.

Our take

GitHub Issues' core value proposition is zero switching cost for teams already living in GitHub. The 2023-2024 Projects v2 overhaul added table views, custom fields, roadmap timelines, and sub-issues — features that put it in legitimate competition with Linear for engineering teams. Copilot-powered issue summaries (Team+) now auto-generate context when you open an issue, reducing the cognitive load of catching up on long threads. The free tier is genuinely unlimited for most use cases. The gap versus Linear is UX and speed: GitHub Issues feels like it was bolted onto a code repository; Linear was designed as a standalone product with keyboard-first workflows and sub-100ms interactions. GitHub Issues wins when your team's entire workflow (code review, CI, deployments) is already in GitHub and you don't want another subscription.

Product roadmap

Microsoft's Copilot push is landing in every GitHub product — expect AI-generated issue descriptions, smart labeling, and PR-to-issue linking automation. The Projects roadmap view is improving iteration-by-iteration. The main ceiling is GitHub's infrastructure — changes must fit within the platform constraints of a repository-centric model, which limits how opinionated the tool can become.

Who is GitHub Issues for?

Solo(1 person)

Great fit

Zero cost included with your GitHub account. Perfectly adequate for solo project tracking without another tool.

Small team(2–20 people)

Great fit

For engineering-only teams already on GitHub, Issues + Projects replaces Linear or Jira for most sprint workflows at $4/seat.

Mid-size(21–200 people)

Good fit

Works well for eng-only orgs. Starts to strain when product managers and designers need dedicated views — GitHub's interface is less accessible to non-engineers.

Large org(201–1,000+)

Mixed fit

Large orgs often run GitHub Issues for engineering and a separate roadmap tool (Productboard, Jira) for cross-functional planning, because GitHub's permissions model isn't designed for stakeholder visibility.