# The issue intake should finish the sorting first > Why GitHub support and community growth get better when the chooser, the form, the discussion handoff, and the maintainer replies sort the work before anyone starts triaging by hand. - Canonical HTML: https://growth.iangoh.com/blog/the-issue-intake-should-finish-the-sorting-first/ - Published: 2026-06-05 - Updated: 2026-06-05T14:05:00Z - Categories: community-led growth, support deflection, seo - Niches: developer tools, open source, AI products, SaaS, creator tools ## On this page - The first gate should decide whether a blank issue deserves to exist - The chooser should route the wrong question somewhere useful - A good form should perform the first round of triage - Useful discussion threads should graduate into tracked work - Maintainer language should be reusable without sounding robotic ## Start with these related tactics - [GitHub issue template chooser with blank issues disabled](/growth-ideas/github-issue-template-chooser-with-blank-issues-disabled/): Disable blank issues for contributors so the GitHub issue chooser forces the public queue through the templates you are actually ready to process. - [GitHub issue template contact links to discussions and security](/growth-ideas/github-issue-template-contact-links-to-discussions-and-security/): Use GitHub issue-template contact links to push support questions and security reports onto the right routes before they become the wrong kind of issue. - [GitHub issue form auto-labels, assignees, and project routing](/growth-ideas/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. A lot of GitHub issue queues look messy because the team starts sorting too late. The maintainer opens the inbox, reads a vague report, asks for the missing details, forwards a product question to Discussions, rewrites the same duplicate note, and only then gets to the real work. By that point the queue is already wasting time. The issue intake should finish the sorting first. ## The first gate should decide whether a blank issue deserves to exist [GitHub issue template chooser with blank issues disabled](/growth-ideas/github-issue-template-chooser-with-blank-issues-disabled/) is the cleanest starting point in this batch. If contributors can always bypass the templates, the maintainer ends up doing form design by comment thread instead. That pairs naturally with [GitHub Discussions category form before question submit](/growth-ideas/github-discussions-category-form-before-question-submit/). One keeps the issue queue structured. The other does the same job on the discussion side. ## The chooser should route the wrong question somewhere useful [GitHub issue template contact links to discussions and security](/growth-ideas/github-issue-template-contact-links-to-discussions-and-security/) fixes a quieter problem. A lot of people are willing to use the right route if the route is visible. If the chooser shows a support discussion path and a security path before submission, fewer threads land in the public bug queue by accident. I would keep that beside [GitHub Discussions sections for announcements, questions, and ideas](/growth-ideas/github-discussions-sections-for-announcements-questions-and-ideas/). Routing works better when the destination has clear lanes too. ## A good form should perform the first round of triage [GitHub issue form auto-labels, assignees, and project routing](/growth-ideas/github-issue-form-auto-labels-assignees-and-project-routing/) matters because it moves queue work to the moment the issue is created. The form is not just asking questions. It is sorting the work. [GitHub issue form required repro steps and environment fields](/growth-ideas/github-issue-form-required-repro-steps-and-environment-fields/) does the same thing for quality. If the first submission already includes reproduction steps, environment details, and relevant files, the maintainer can decide instead of interrogate. That is the same structural lesson behind [doc category index for community knowledge base](/growth-ideas/doc-category-index-for-community-knowledge-base/). Good public support scales when the first artifact is structured enough to become a durable reference later. ## Useful discussion threads should graduate into tracked work [GitHub discussion thread to issue with label carryover](/growth-ideas/github-discussion-thread-to-issue-with-label-carryover/) is the bridge move in this cluster. It keeps the conversation public, keeps the labels, and still gives the team a real issue to track. That is much better than copying the thread into a fresh ticket and losing half the context. I like it next to [GitHub Discussions Q&A category with marked answers](/growth-ideas/github-discussions-q-and-a-category-with-marked-answers/). Some threads should become canonical answers. Others should become tracked work. The system gets healthier when those forks are explicit. ## Maintainer language should be reusable without sounding robotic [GitHub saved replies for triage and duplicate routing](/growth-ideas/github-saved-replies-for-triage-and-duplicate-routing/) looks small until the queue gets busy. Once a team has to repeat the same duplicate note, repro request, or handoff explanation ten times a day, saved replies stop being a convenience and start being infrastructure. This cluster is strongest for developer tools, open-source products, AI products with public repos, SaaS teams that run support through GitHub, and creator tools with active user feedback loops. If I were tightening one repo this week, I would close the blank issue escape hatch for contributors, add contact links for support and security, let the form auto-route new work, require the repro details that usually cost a second comment, graduate real product discussions into issues, and standardize the maintainer replies that already repeat every day. If you want help turning support queues, docs surfaces, and public feedback systems into cleaner growth assets, the advisory CTA is here: [work with Ian Goh](https://iangoh.com/advisory). ## Related GrowthDex tactics - [GitHub issue template chooser with blank issues disabled](/growth-ideas/github-issue-template-chooser-with-blank-issues-disabled/) - GitHub, Support, Community - [GitHub issue template contact links to discussions and security](/growth-ideas/github-issue-template-contact-links-to-discussions-and-security/) - GitHub, Community, Security - [GitHub issue form auto-labels, assignees, and project routing](/growth-ideas/github-issue-form-auto-labels-assignees-and-project-routing/) - GitHub, Operations, Support - [GitHub issue form required repro steps and environment fields](/growth-ideas/github-issue-form-required-repro-steps-and-environment-fields/) - GitHub, Support, Product-led Growth - [GitHub discussion thread to issue with label carryover](/growth-ideas/github-discussion-thread-to-issue-with-label-carryover/) - GitHub, Community, Product feedback - [GitHub saved replies for triage and duplicate routing](/growth-ideas/github-saved-replies-for-triage-and-duplicate-routing/) - GitHub, Support, Community ## Essay chronology - [Newer essay: The repository should answer the trust question first](/blog/the-repository-should-answer-the-trust-question-first/) - community-led growth, brand trust, seo - [Older essay: The community archive should answer the next visitor](/blog/the-community-archive-should-answer-the-next-visitor/) - community-led growth, SEO, documentation ## Keep reading - [The repository should answer the trust question first](/blog/the-repository-should-answer-the-trust-question-first/) - community-led growth, brand trust, seo - [The launch page should hand people somewhere to stay](/blog/the-launch-page-should-hand-people-somewhere-to-stay/) - community-led growth, launch strategy, seo - [The forum should keep the answer after the chat scrolls away](/blog/the-forum-should-keep-the-answer-after-the-chat-scrolls-away/) - community-led growth, support deflection, forum seo ## Continue through the blog - [SaaS](/blog/#path-saas) - 3 essays in this path - [AI products](/blog/#path-ai-products) - 3 essays in this path - [developer tools](/blog/#path-developer-tools) - 3 essays in this path ## Sources - [GitHub Docs: Configuring issue templates for your repository](https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository) · [GrowthDex source hub](/sources/github-docs-configuring-issue-templates-for-your-repository-docs-github-/) - [GitHub Docs: Syntax for issue forms](https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms) · [GrowthDex source hub](/sources/github-docs-syntax-for-issue-forms-docs-github-com/) - [GitHub Docs: Syntax for GitHub's form schema](https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema?apiVersion=2022-11-28) · [GrowthDex source hub](/sources/github-docs-syntax-for-github-s-form-schema-docs-github-com/) - [GitHub Docs: Creating an issue](https://docs.github.com/en/issues/tracking-your-work-with-issues/using-issues/creating-an-issue) · [GrowthDex source hub](/sources/github-docs-creating-an-issue-docs-github-com/) - [GitHub Docs: About saved replies](https://docs.github.com/en/get-started/writing-on-github/working-with-saved-replies/about-saved-replies) · [GrowthDex source hub](/sources/github-docs-about-saved-replies-docs-github-com/) ## Editing notes - Kept the essay on one operational claim about sorting work earlier instead of turning it into a generic GitHub best-practices list. - Used concrete objects like blank-issue gates, contact links, label carryover, repro fields, and saved replies instead of inflated community language. - Cut abstract platform talk and let the queue mechanics carry the argument from paragraph to paragraph. - Ended on a real repo cleanup sequence and direct advisory CTA instead of a padded conclusion. ## Advisory If you want help turning this into a growth system, Ian Goh offers advisory at https://iangoh.com/advisory.