Feature Request Template: What to Ask (Free, Copy-Paste)

A feature request template does two jobs at once, and they pull in opposite directions. It needs to gather enough context that the request is actionable — and stay short enough that people actually submit it. Get the balance wrong in either direction and you either drown in vague one-liners or scare everyone off with a form that feels like a job application. Here's a template that threads the needle, plus the reasoning so you can adapt it.

The copy-paste template

What would you like to see? (One sentence describing the feature or change.)

What problem would this solve for you? (What are you trying to do, and what's getting in the way today?)

How do you handle this now? (Your current workaround, if any.)

How important is this to you? (Nice-to-have / Would use often / Blocking me)

Four fields. Only the first is truly required; the rest are optional but valuable. That's the whole point — you ask for context without demanding it.

Why each field earns its place

"What would you like to see?" forces a single, clear statement. It becomes the request title and the thing others vote on, so it needs to be crisp.

"What problem would this solve?" is the most important field, because it separates the request from the underlying need. Users ask for solutions ("add a dropdown here"), but the need behind it ("I can't filter my list fast enough") often has a better solution than the one they imagined. Capturing the problem lets you solve it your way.

"How do you handle this now?" reveals urgency and reveals whether a workaround already exists. A painful workaround signals real demand; "I just don't do it" signals a nice-to-have.

"How important is this?" gives you a quick severity read that votes alone don't capture — the difference between "would be nice" and "I'm about to churn over this."

Keep it optional, keep it short

The cardinal rule: the more required fields you add, the fewer requests you get. Every mandatory box is a reason to close the tab. Make only the first field required and let motivated users fill in the rest. You'll get more submissions and richer detail on the ones that matter, because the people with a real problem are happy to explain it.

This is also why a public board beats a long form. On FeatureRequest, users post a short request and others add context by voting and commenting — the detail accumulates socially instead of front-loading onto one person. For building the input itself, see our guide on how to build a feature request form people actually use, and for what good ones look like, feature request examples.

Put the template to work

Templates are only useful where people can find them. Drop this one into a public board so requests are captured, ranked, and visible. Create a free board on FeatureRequest, adapt the template to your product, and start collecting requests you can actually act on.