# Bug-vs-feature-request template split at intake

> Split intake into separate bug and feature-request templates before the queue starts growing so each report enters triage with the right shape and destination.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/bug-vs-feature-request-template-split-at-intake/
- Source: [linear.app](https://linear.app/now/cx-in-linear)
- GrowthDex source hub: [Linear](/sources/linear-linear-app/)
- Last checked: 2026-05-27
- Rarity: rare
- Budget: free
- Channels: Support, Product, Slack
- Stages: triage, support-led growth, intake quality, prioritization
- Key metric: Linear maintains 2 intake templates, one for bugs and one for feature requests

## Why this can grow

Teams lose time when every incoming report has to be reclassified by hand. A simple bug versus feature split pushes the first routing decision to the edge of the system, where the context is freshest. That makes triage faster, duplicate detection cleaner, and the follow-up more credible because customers can feel the company already knows what kind of work this is.

## 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 bug-vs-feature-request template split at intake can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Support and Product channel.
3. Use the evidence from linear.app 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

Linear uses separate templates in Intercom and Linear Asks for bugs and feature requests, routing each one into the matching triage queue.

## Adjacent tactics in the same lane

- [Minimum required fields for fast feedback filing](/growth-ideas/minimum-required-fields-for-fast-feedback-filing/) - same source, 2 shared channels, 2 shared stages
- [Enterprise-tier bug routing with auto-urgent SLA](/growth-ideas/enterprise-tier-bug-routing-with-auto-urgent-sla/) - same source, 2 shared channels, 2 shared stages
- [Weekly CX on-call for off-platform feedback](/growth-ideas/weekly-cx-on-call-for-off-platform-feedback/) - same source, 2 shared channels, 1 shared stage
- [Channel-specific notification queues for external feedback](/growth-ideas/channel-specific-notification-queues-for-external-feedback/) - same source, 2 shared channels, 1 shared stage

## Read GrowthDex essays

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

## Related GrowthDex essays

- [The request system should sort pain before the roadmap sees it](/blog/the-request-system-should-sort-pain-before-the-roadmap-sees-it/) - support-led growth, product ops, brand trust

## Advisory

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