# GitHub issue form auto-labels, assignees, and project routing

> Route a GitHub issue at creation time with default labels, assignees, projects, and issue type instead of leaving the queue to sort itself later.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/github-issue-form-auto-labels-assignees-and-project-routing/
- Source: [docs.github.com](https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms)
- GrowthDex source hub: [GitHub Docs: Syntax for issue forms](/sources/github-docs-syntax-for-issue-forms-docs-github-com/)
- Last checked: 2026-06-05T14:05:00Z
- Rarity: rare
- Budget: free
- Channels: GitHub, Operations, Support
- Stages: workflow automation, triage routing, queue hygiene, issue operations


## Why this can grow

Issue triage gets expensive when every new report enters the same untyped pile and waits for a maintainer to tag, assign, and route it by hand. GitHub issue forms allow the form itself to apply default labels, assignees, projects, and issue type when the issue is created. That means the sorting happens at the moment of contribution, not in a later cleanup sweep. The form becomes part intake, part workflow automation, which is often enough to keep a support queue usable without another external tool.

## Ian's take

From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. My bias is to treat this as a small market test first. Make the audience narrow, make the promise concrete, and let the first real response decide whether it deserves more work. I would run it small enough to learn quickly, then only scale the parts that real users repeat, save, reply to, or buy from. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.

## Action plan

1. Define one narrow startup segment where github issue form auto-labels, assignees, and project routing can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the GitHub and Operations channel.
3. Use the evidence from docs.github.com to set the first version of the message, format, and audience.
4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.

## Source-backed example

GitHub Docs lists `labels`, `assignees`, `projects`, and `type` as top-level issue-form keys, with example values like `labels: ["bug", "triage"]` and `projects: ["octo-org/1", "octo-org/44"]`.

## Adjacent tactics in the same lane

- [Discourse category approval rules by trust group](/growth-ideas/discourse-category-approval-rules-by-trust-group/) - 2 shared channels, 1 shared stage
- [Required tagging before archive or move](/growth-ideas/required-tagging-before-archive-or-move/) - 2 shared channels, 1 shared stage
- [Snoozed triage that returns on new activity](/growth-ideas/snoozed-triage-returns-on-new-activity/) - 2 shared channels, 1 shared stage
- [GitHub contributing tab before first PR](/growth-ideas/github-contributing-tab-before-first-pr/) - 2 shared channels

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The issue intake should finish the sorting first](/blog/the-issue-intake-should-finish-the-sorting-first/) - community-led growth, support deflection, seo

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.