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.
Why this can grow a startup
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.
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.
Source-reported evidence
Source: Linear · Browse Linear tactics
Linear maintains 2 intake templates, one for bugs and one for feature requests
Attributed to the cited source; GrowthDex has not independently verified it. Use this as context, not as a forecast, benchmark, or recommended target.
Evidence scope: claims and metrics are attributed to the linked source; GrowthDex has not independently replicated the reported result. Check the original context and validate fit before applying it. Read the evidence methodology.
Source discovered: May 27, 2026
When to use it
Use this when Support, Product, Slack is relevant to triage, support-led growth, intake quality and you can run a bounded test with a free budget.
When not to use it
Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.
How to do it
- Choose one target segment and define the exact next action this tactic should prompt.
- Adapt the tactic to Support and Product, using evidence from Linear as context—not as a promised result.
- Record a baseline for: Users who resolve the issue and complete the next useful action. Set a guardrail that would make you pause the test.
- Run a narrow pilot and choose a test window that fits the normal decision or use cycle; do not scale before you have observed the full cycle.
- Compare the signal with its baseline. Scale only if the intended action improves without crossing the guardrail; otherwise revise one variable or stop and record what you learned.
Compare a stack for your situation
Compare source-backed tactics against your product, stage, budget and channel strengths, then choose one experiment to test.
Explore the context
Did you launch this experiment?
Report a launch to help us understand which growth ideas founders put into practice.
Apply this with an operator
Choose product surfaces that compound distribution without hiding weak activation or retention.
SOURCE HUB
More tactics from Linear
Explore related GrowthDex examples and evidence connected to Linear.
Open Linear source hub