---
title: "Feature Request Template: 14 Forms and Tools Worth Using"
description: "A feature request template asks for the problem, use case, workaround, who asked and impact. Copy ours, or start from 14 free forms and boards."
canonical: https://luckpanda.app/blog/feature-request-template
author: "Dhrumil Barot"
author_bio: "Dhrumil is a small-business operations and compliance expert. Dhrumil built LuckPanda so small businesses can run invoicing, inventory, accounts and compliance in one place."
published: 2026-11-13
updated: 2026-11-13
category: "Customer support and chat"
keywords: "feature request template"
language: en
---

# Feature Request Template: 14 Forms and Tools Worth Using

A feature request template asks for the problem, use case, workaround, who asked and impact. Copy the 9-field template, or start from 14 free forms and boards.

By [Dhrumil Barot](https://luckpanda.app/about#founder), Founder. Published 13 Nov 2026. Updated 13 Nov 2026. 9 min read.

**TL;DR:** A good feature request template asks for the problem before the solution: what the person is trying to do, what stops them, how they cope today, who they are and how often it hurts. Copy the 9-field template below, put it where requests already arrive (GitHub, Linear, Notion, a form or a feedback board), then count and score requests instead of debating them one by one.

A feature request template is a structured form that turns "can you add X?" into something a product team can compare and decide on. The fields that matter are the request title, the problem, the use case, the current workaround, who is asking (role and account), how often the problem occurs, how important it is to them, supporting evidence, and a status your team owns. Free ready-made versions exist for GitHub issue forms, GitLab, Linear, Notion, Google Forms, Tally, Jotform and Fillout, and free feedback boards such as Canny, Fider and Jira Product Discovery handle voting and tracking. This page gives you the template, the 14 resources with what each costs and when to use it, and a way to catch the requests customers mention in chat but never submit.

## What should a feature request template include?

A feature request template should include the problem, the context of the person asking and a status your team controls; the proposed solution is optional. Requesters know their pain better than the best fix, so the problem field does the most work. Here is a template you can copy into any form, issue tracker or doc:

1. **Feature title:** a short name, under 80 characters, written as the outcome ("Export the dashboard as PDF").
2. **Problem:** what are you trying to do, and what stops you today?
3. **Use case:** when and how often would you use this? (Daily / Weekly / Monthly / Rarely)
4. **Current workaround:** how do you handle it now, and what does it cost you in time (for example 15 minutes per week)?
5. **Importance:** Nice to have / Important / Blocking.
6. **Proposed solution (optional):** if you have an idea of how it should work, describe it.
7. **Who is asking:** name, role and company or account. Fill this in for them if it comes from a logged-in user.
8. **Evidence:** screenshots, a link, the original message or chat transcript.
9. **Status (internal):** New / Under review / Planned / Shipped / Not planned, plus the date you replied.

Fields 1 to 5 go on a customer-facing form. Field 7 is often captured automatically, and field 9 is for your team only. Internal versions for sales and support add the account's plan, the deal or renewal at stake and how many other customers asked.

![Which feature request fields go on the customer form and which your team fills in](https://cdn.sanity.io/images/pcmcvz9y/production/452207ccd6a98386ceebf859fd83ddff95cbdcdf-1344x548.png?w=1200&auto=format&fit=max)

*Keep the public form to five or six fields; add context on your side.*

Keep the public form short: aim for under 2 minutes to complete. Every extra required field costs submissions, and the context you need (plan, account size, how many others asked) is something you can add yourself.

## Where can I get a free feature request form template?

You can get a free feature request form template from the issue tracker you already use (GitHub, GitLab, Linear), from a document tool (Notion, Google Forms) or from a form builder (Tally, Jotform, Fillout, WPForms). Pick by where your requesters already are: developers on GitHub, internal teams in Linear or Slack, customers on your website.

### Templates inside issue trackers

- [GitHub issue forms](https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms): for open-source projects and developer tools. Free. You add a YAML file to the .github/ISSUE_TEMPLATE folder with a name, description and body; fields can be text inputs, text areas, dropdowns, checkboxes and file uploads. Worth it because required fields stop half-empty requests, though "required" only works in public repositories, and labels in the form are only applied if they already exist in the repo.
- [GitHub's form schema reference](https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema): the field-by-field reference for the forms above, including the min_length validation that forces a real problem description. Free. Copy its examples rather than typing YAML from scratch: indentation errors are the most common reason a form fails to load.
- [GitHub discussion category forms](https://docs.github.com/en/discussions/managing-discussions-for-your-community/creating-discussion-category-forms): for an "Ideas" category where people discuss and upvote before anything becomes an issue. Free. Same schema, stored in /.github/DISCUSSION_TEMPLATE/, so you can reuse your issue form fields.
- [GitLab description templates](https://docs.gitlab.com/user/project/description_templates/): for teams on GitLab. Available on the Free tier. A Markdown file in .gitlab/issue_templates on the default branch appears in the "Choose a template" dropdown; it is a text template, not a form, so nothing is enforced.
- [Linear form templates](https://linear.app/docs/issue-templates): for product teams that triage in Linear. Form templates support text, long text, dropdown, checkbox, date and instruction fields, plus property fields such as customer, priority and due date, and any field can be required. Linear Asks, which turns Slack messages, emails and web forms into issues, is on the Business and Enterprise plans and is designed for internal requests ([Linear Asks docs](https://linear.app/docs/linear-asks)).

[Get started with GitHub issue forms - GitHub Checkout](https://www.youtube.com/watch?v=qQE1BUkf2-s&t=46s) (GitHub)

A GitHub engineer builds an issue form live: where the YAML file goes, how to copy a dropdown from the docs, how the required flag works, and what the form looks like to the person filing it. The same steps build a feature request form.

- [1:09](https://www.youtube.com/watch?v=qQE1BUkf2-s&t=69s) Templates live in .github/ISSUE_TEMPLATE and end in .yml
- [2:19](https://www.youtube.com/watch?v=qQE1BUkf2-s&t=139s) Copying a dropdown field from the docs keeps the YAML spacing
- [2:43](https://www.youtube.com/watch?v=qQE1BUkf2-s&t=163s) Validations required makes a field mandatory
- [3:05](https://www.youtube.com/watch?v=qQE1BUkf2-s&t=185s) Filling in the form as a contributor
- [5:25](https://www.youtube.com/watch?v=qQE1BUkf2-s&t=325s) Most invalid templates are spacing errors

### Templates in docs and form builders

- [Notion Feature Requests template](https://www.notion.com/templates/feature-requests): for small teams that want a request database without new software. Free, published by Notion. It rates 4.8 out of 5 from 14 ratings on Notion's marketplace; one reviewer's tip is to add a priority column, which you should.
- [Google Forms](https://support.google.com/docs/answer/6281888): for anyone with a Google account. Free. There is no official feature request template, so build one from the 9 fields above; create it from Google Sheets (Tools, then Create a new form) and every response lands as a row you can sort and tag.
- [Tally feature request form](https://tally.so/templates/feature-request-form-template/kwo55m): for a clean public form on a website. Tally's free plan has unlimited forms and submissions within fair use ([Tally pricing](https://tally.so/pricing)), including file uploads and conditional logic, so you can show the workaround question only when someone picks "Blocking".
- [Jotform feature request form](https://www.jotform.com/form-templates/feature-request-form): for teams that want to send responses to a CRM or other apps. The free Starter plan includes templates; free forms carry Jotform branding ([Jotform pricing](https://www.jotform.com/pricing/)).
- [Fillout feature request form](https://fillout.com/templates/feature-request-form): for teams that store requests in Airtable or Notion. Free plan: unlimited forms and 1,000 responses per month ([Fillout pricing](https://www.fillout.com/pricing)).
- [WPForms feature request template](https://wpforms.com/templates/feature-request-form-template/): for WordPress sites. Its default fields are name, email, product dropdown, feature requested and how the feature would work. Add a problem field before you publish, because "how should it work" alone invites solutions without context.

## How do you track and prioritize feature requests?

You track feature requests by putting every one in a single list, merging duplicates so each idea has a count of who asked, and giving each a status. You prioritize them with a simple score rather than by who shouted loudest. A spreadsheet works up to a few hundred requests; past that, a feedback board saves the merging and the "we shipped it" emails.

### Feedback boards with free plans

- [Canny](https://canny.io/pricing): for SaaS teams that want a public voting board and changelog. Free plan: 25 tracked users (anyone who posts, votes or comments), 5 managers and unlimited feedback; Pro starts at $79 per month, billed yearly.
- [Fider](https://fider.io/pricing): for teams that want a simple voting board or to self-host. The hosted free plan has a fair use limit of 250 feedback requests and the paid plan is $25 per month; the code is open source under AGPL-3.0 on [GitHub](https://github.com/getfider/fider).
- [Jira Product Discovery](https://www.atlassian.com/software/jira/product-discovery/pricing): for teams already in Jira that want ideas, insights and scoring next to delivery work. Free for up to 3 creators; Standard is $10.50 per creator per month, and contributors are free.

### Prioritization method

- [RICE scoring by Intercom](https://www.intercom.com/blog/rice-simple-prioritization-for-product-managers/): the original write-up by Sean McBride. Free. RICE score = Reach x Impact x Confidence / Effort, with impact on a fixed scale (3 massive, 2 high, 1 medium, 0.5 low, 0.25 minimal), confidence as 100%, 80% or 50%, and effort in person-months.

Here is RICE applied to three requests a small software business might receive in one quarter:

![RICE scores for three feature requests, with the CSV export scoring highest](https://cdn.sanity.io/images/pcmcvz9y/production/f70c166b8b61217fc6a31d0e8dacf08c10c9e66b-1344x410.png?w=1200&auto=format&fit=max)

*Score = Reach x Impact x Confidence / Effort. Effort in person-months.*

Dark mode had the most votes (900 per quarter), but the CSV export wins with a reach of 400 per quarter: fewer people, a bigger effect on each, a sure estimate and half the effort. SSO scores low on reach, yet if those 60 users sit in two accounts up for renewal, that is the business context field doing its job: the score starts the conversation, it does not end it.

A workable weekly routine, about 30 minutes per week for a small team:

1. Collect every new request into the one list (form responses, issues, support tickets, sales notes).
2. Merge duplicates and add the requester to the existing item, so the count stays honest.
3. Tag each item by area. Our guide to [customer feedback categories](https://luckpanda.app/blog/customer-feedback-categories) has a set of tags that works for most small businesses.
4. Score the items that crossed a threshold (for example 5 requesters) with RICE.
5. Change the status and reply to everyone who asked within 7 days, including the "not now" answers.

## How do you collect feature requests from customers who never fill in a form?

Most customers never fill in a feature request form. They mention the missing thing in passing: in a support ticket, a sales call or a website chat ("do you deliver on Sundays?", "can I pay in instalments?", "does it work with Shopify?"). Those questions are feature requests in disguise, and they come from people at the moment they were deciding whether to buy.

![How a question in a chat becomes a ranked feature request](https://cdn.sanity.io/images/pcmcvz9y/production/c5aa66fa9c821a3c9e3eb795f9b1777c77bde800-1344x326.png?w=1200&auto=format&fit=max)

*The count comes from people who asked, not from people who found your form.*

To catch them:

- **Read transcripts on a schedule.** Every 7 days, search chat and ticket transcripts for phrases such as "do you have", "can I", "is there a way" and "I wish". Log each one with the field template above, with the transcript as evidence. Our guide on turning [website chats into voice of customer data](https://luckpanda.app/chatbot/guides/voice-of-customer-from-chats) walks through the tagging.
- **Give support a one-click path.** Agents should be able to log a request from inside the conversation, with the customer and account attached automatically. Canny's and Linear's integrations do this for the tools they support.
- **Count people, not mentions.** One customer asking five times is one request with high importance, not five requests.

This is the problem [LuckPanda Chatbot](https://luckpanda.app/chatbot) is built around. It answers website visitors from your own pages and documents, and with request logging on, the things visitors ask for that you do not offer yet are grouped on a Requests board, ranked by how many different people asked, with a weekly digest. It costs $4.99 per month for up to 10 websites (₹199 per month in India), and you can build and test one from your website address without an account.

## How do you reply to customers who suggest a feature?

Reply within 2 business days, thank the person for the specific idea, say what happens next, and never promise a date you do not control. Three replies cover most cases:

- **Logged:** "Thanks, \[name\]. Exporting the dashboard as a PDF is a clear use case, and I've added it to our request list with your note that the Monday report takes you 15 minutes by hand. We review requests every month and I'll write back when its status changes."
- **Planned:** "Good news: PDF export is planned for this quarter. I've linked your request so you'll hear from us the day it ships. Until then, the print view (File, then Print, then Save as PDF) keeps the charts."
- **Not now:** "We've decided not to build PDF export this year because most teams share a live link instead. I know that doesn't help with your manager, so here's how to share a view-only link without a login."

For more ready-made wording, the [canned responses library](https://luckpanda.app/chatbot/tools/canned-responses-library) has replies for common support situations you can adapt.

## Feature request vs bug report: what is the difference?

A feature request asks for something the product does not do; a bug report says the product does not do what it is supposed to. The test is expected behaviour: if the documentation or the interface says it should work and it doesn't, it is a bug. Many requests sit in between ("search ignores tags"), so a simple dropdown on the form (Bug, Feature request, Not sure) lets requesters pick and your team reclassify during triage. Keep separate templates: a bug report needs steps to reproduce and an environment, which a feature request form should not ask for.

## Start here: a path for a small team

1. Copy the 9-field template into a Tally, Google or Notion form this week.
2. Link the form from your help page, your app's menu and your support signature.
3. Add requests you hear in chats and calls yourself, with the transcript as evidence.
4. Once a month, merge duplicates, score the top ten with RICE and reply to everyone.
5. Move to a feedback board (Canny, Fider or Jira Product Discovery) when the spreadsheet passes a few hundred rows or you want public voting.

## Questions

### What is a feature request template?

A feature request template is a standard set of questions for anyone suggesting a new feature or an improvement: the problem, the use case, the current workaround, importance and who is asking. It makes requests complete on arrival and comparable with each other, so a team can count and prioritize them instead of chasing details.

### How do you write a good feature request?

Start with the problem and the situation, not the solution: what you were trying to do, what stopped you and how you work around it today. Add how often it happens, how much it matters and an example or screenshot. A proposed solution is welcome but optional, because the team may know a better fix.

### Is there a feature request template in Jira?

Atlassian's tool for this is Jira Product Discovery, which is built for collecting, scoring and prioritizing ideas next to Jira work, and is free for up to 3 creators; contributors who only add and comment are free users. Inside Jira itself, teams usually log requests as a Story or a custom feature request issue type.

### Should feature request forms be public or internal?

Use both. A short public form or voting board captures customers' own words, and an internal template lets sales and support add context customers cannot, such as plan, account size and renewal dates. Route both into the same list so duplicates merge.

### How many fields should a feature request form have?

Five or six on a public form is enough: title, problem, use case and frequency, current workaround, importance and an optional proposed solution. Fill in the requester's details and the status yourself. Long required forms reduce how many people submit at all.

### How do you say no to a feature request?

Thank the person for the specific idea, explain the reason in one sentence (it does not fit who the product is for, or something else ranks higher), offer a workaround if there is one and leave the request open for votes. Answering "not now" within 2 days keeps trust better than leaving the request without a reply for weeks.

## More guides

- [California Bot Disclosure Law: SB 1001 Chatbot Reference](https://luckpanda.app/blog/california-bot-disclosure-law)
- [Chatbot Fallback Message: 10 Examples to Copy](https://luckpanda.app/blog/chatbot-fallback-message)
- [What Is Speed to Lead? Definition, Formula and Examples](https://luckpanda.app/blog/speed-to-lead)

## Related tools

- [Invoice generator](https://luckpanda.app/tools/invoice-generator): Bill a client in any currency, with tax worked out as you type.

## About the author

**Written by [Dhrumil Barot](https://luckpanda.app/about#founder)**, Founder. Dhrumil is a small-business operations and compliance expert. Dhrumil built LuckPanda so small businesses can run invoicing, inventory, accounts and compliance in one place. [LinkedIn](https://www.linkedin.com/in/bdhrumil) · [X](https://x.com/fyidhrumil)