GitHub issue types and fields reach personal accounts, up to 25 of each

GitHub has made issue types and issue fields generally available on repositories owned by personal accounts, so solo developers and small teams get the same planning tools as organisations.

On 11 November 2026 GitHub announced that issue types and issue fields are now generally available on repositories owned by personal accounts. Until now these planning features were an organisation-level tool.

What GitHub says

Why a non-developer should care

Many early-stage products start in a freelancer’s or founder’s personal GitHub account. Until now, the work tracked there was a flat list of issues with free-text labels. With typed issues and structured priority and effort fields, you can ask for a status view that does not depend on someone’s memory: how many bugs, how big, what is due.

It also gives AI coding agents better-structured work to pick up, because a well-typed issue with an effort estimate is a clearer brief than a one-line title.

So what

If your product’s repository sits in a personal account, ask your developer to switch these fields on and report from them. If it should live in an organisation account instead, that is a governance conversation worth having early. Our AI-assisted development service sets up delivery tracking like this from day one. To talk it through, start a project.

← All research

More research.

GitHub Copilot adds Supabase, Webflow, Wix and five more connectors in public preview

GitHub Copilot now connects to eight more services, including Supabase, Webflow, Wix and Mixpanel, through verified MCP connectors in public preview. They join more than 25 existing ones.

Read ›

Gemini 4 Neon is generally available in GitHub Copilot, aimed at lower-cost agentic coding

Gemini 4 Neon is now generally available in GitHub Copilot for agentic coding. Google says its quality is close to Gemini 4 Carbon at a lower token cost per task.

Read ›

Claude Code 2.1.328 brings auto mode to Bedrock, Vertex and Foundry, and narrows /code-review to bugs

Claude Code 2.1.328 extends auto mode to Claude Opus 4.6 and Sonnet 4.6 on Amazon Bedrock, Google Cloud and Microsoft Foundry. /code-review now reports only bugs and CLAUDE.md violations.

Read ›

GitHub Copilot Evals: repeatable tests for AI agents, now in public preview

GitHub Copilot Evals lets teams write repeatable tests for AI coding skills, custom agents and MCP tools. It checks both the result and the path the agent took, and is in public preview.

Read ›

GitHub Copilot can now drive your browser: browser use enters public preview

GitHub Copilot browser use lets an AI coding agent control Chrome to debug web apps and run browser tests. It is in public preview across the CLI, the Copilot app, VS Code and JetBrains.

Read ›

Claude Code 2.1.327 refuses some symbolic links and lists broken setup in /status

Claude Code 2.1.327 tightens file and package permissions again and adds a /status list of broken agent, skill and hook settings. A short read for teams using AI coding tools on a live product.

Read ›

Start a project

Building with AI? Let's talk.

Tell us what you are building. We'll give you an honest view of the right approach.

Start a projectSee our work