KjerrA feature request template
you can copy.
A good feature request template asks for the problem, not the solution: what someone is trying to do, what gets in the way, who is affected and what good looks like. Copy the template below into a doc, a form or an issue tracker, or use a board that asks the same questions for you.
The feature request template
Six prompts. Only the title should be required.
Title
One line that names the outcome, not the solution.
Example: Export reports to CSV
What are you trying to do?
The task, in your own words.
What gets in the way today?
What you do now instead, and what it costs you.
Who is affected, and how often?
Just you, your team, every customer on a plan? Daily, monthly?
What would a good result look like?
How you would know it is solved. Leave the design to the team.
Anything to show?
A screenshot, an example file, a link.
Why each field is there
- Title. An outcome in one line makes requests searchable and lets duplicates find each other.
- What are you trying to do? The goal survives even when the proposed solution does not.
- What gets in the way? The workaround tells you how much the problem costs.
- Who and how often? Reach and frequency: the Reach of a RICE score, in the user's words.
- What would good look like? An acceptance test in the user's words.
- Anything to show? A screenshot replaces three paragraphs.
Turning the template into a feature request form
A feature request form should be shorter than the template. Keep the title and one open question on the form, and ask the rest in a comment when you need it.
- Require the title only.
- Show similar requests before the form is submitted, so people can vote instead.
- Let people attach a screenshot by pasting it.
- Confirm the email once, not on every request.
- Say what happens next: where the request appears and how they will hear back.
Using it as a product feedback template
The same prompts work as a product feedback template for bugs and general comments. Keep the first question open and drop the last two. Where the form fits in the wider process is covered in customer feedback best practices.
- For bugs, ask what they expected and what happened instead. The bug report template has the full set of prompts.
- For praise and complaints, the first two prompts are enough.
- Keep everything in one list, so a complaint and a request about the same thing meet.
How Kjerr's idea form covers the template
The idea form you get when you manage feature requests in Kjerr starts as the short version: a title, optional details and screenshots. The rest of the template is handled by the board around the form.
- The details field asks: “What are you trying to do, and what gets in the way?”
- Up to 5 screenshots or files of 10 MB each.
- Similar ideas appear while the title is typed, each with a vote button.
- Who is affected comes from votes and from Users & Companies, with company, plan and MRR.
- The form is yours to edit: rename the two built-in fields, mark details as required, and add up to eight fields of your own, each one line or a paragraph.
Questions, answered plainly.
What is a feature request template?
A feature request template is a short set of prompts that helps a user describe what they need: the goal, what blocks them today, who is affected and what a good result looks like. It makes requests comparable and saves the team a round of follow-up questions.
What should a feature request form ask?
As little as possible. A title and one open question collect more requests than ten required fields. Ask for the problem, not the solution, and let people add a screenshot.
Should a feature request form have required fields?
Only the title. Every extra required field lowers the number of people who finish the form, and the detail can be asked for later in a comment.
How is a product feedback template different?
A product feedback template covers anything a user wants to say, including bugs and praise; a feature request template is the part about things that do not exist yet. The same prompts work for both if the first question stays open.
How does Kjerr's idea form compare to this template?
By default it asks for a short title and optional details, with the prompt “What are you trying to do, and what gets in the way?”, and takes up to 5 screenshots or files. You can rename both fields and add up to eight of your own. While the title is typed, similar ideas appear with a vote button, so many requests become a vote instead of a duplicate.
Related pages
Give your users an answer.
Kjerr is free during early access, with every feature included and no credit card. When paid plans arrive they will be priced per workspace, never per admin seat and never per tracked user, so the number of people who post, vote or comment never changes the bill.