Skip to content

A good feature request says what problem a user has, who has it and what they do today. Pick a format, fill in what you know, and copy or download it as Markdown. Runs in your browser; nothing is sent or stored.

Format

Markdown preview

# Feature request

## Problem

_What is hard or impossible today, in the user’s words_

## Who has this problem

_Role, plan or customer segment_

## Current workaround

_What they do today instead_

## Proposed solution

_One idea, not a full spec_

For GitHub, save the file as .github/ISSUE_TEMPLATE/feature_request.md. Examples of all three formats are in our feature request template guide.

Collect requests without the copy-paste

A template helps one request. A feedback board collects all of them, counts votes, merges duplicates, and tells every requester when the feature ships.

See feature request software, add an in-app feedback widget, or read how to go from feedback to roadmap.

Frequently Asked Questions

Common questions about feature request templates.

Have more questions?

A title, the problem the user has, who has it, what they do today instead, and a proposed solution. Templates for product teams add evidence (votes, accounts, deal value) and one success metric.

Yes. It runs in your browser, needs no signup, and nothing you type is sent to a server or stored.

Yes. Pick the GitHub issue format, download the file, and save it as .github/ISSUE_TEMPLATE/feature_request.md in your repository.

Ask for it, but weigh the problem more. Customers know their problem best; the team usually finds a better solution once it sees several requests for the same problem.

Into one shared list where others can vote and comment, such as a feedback board. That keeps duplicates together and lets you tell every requester when the feature ships.

Updated November 2026

Join us

Turn requests into a ranked list

Pay only for team seats: 5 seats from $60/mo. 14-day free trial, no credit card.