Feature Request Template
6 free, ready-to-use feature request templates for Google Sheets, Notion, Jira, Linear, and Trello. With field guides, real examples, and honest pros and cons for each format.
Or skip templates entirely — let users submit and vote on requests with Features.Vote
Browse 6 templatesWhat Every Feature Request Template Needs
Regardless of which tool you use, these are the fields that separate useful feature requests from vague wishlists.
| Field | Why It Matters | Example | Required? |
|---|---|---|---|
| Feature Title | A clear, one-line summary that anyone on the team can understand at a glance. | "Add CSV export to the analytics dashboard" | |
| Description | What the feature should do, in 2-3 sentences. Focus on the outcome, not the implementation. | "Users need to export their analytics data as CSV files so they can build custom reports in Excel and share them with stakeholders who don't have product access." | |
| Use Case / Problem | Why the user needs this. What problem are they trying to solve? This is the most important field for prioritization. | "Our finance team requests weekly reports that I currently compile manually by screenshotting charts. This takes 2 hours every Monday." | |
| Requester | Who submitted the request — name, email, company, and plan tier. Helps you weigh requests by customer value. | "Jane Smith, Acme Corp (Growth plan, $29/mo)" | |
| Priority | How urgent is this for the requester? Use a simple scale: Nice-to-have, Important, or Critical. | "Critical — blocking our team from adopting the product fully" | Optional |
| Category | Tag by product area or type: UX, API, Integration, Performance, New Feature, Mobile. Helps with sprint planning. | "Integration — relates to our existing analytics pipeline" | Optional |
| Status | Track where each request stands: New, Under Review, Planned, In Progress, Shipped, or Declined. | "Under Review — discussed in Q2 planning, awaiting effort estimate" | |
| Votes / Request Count | How many users have asked for this same thing? The single best signal for prioritization. | "14 users requested this (7 on Growth plan, 5 on Lite, 2 on trial)" | Optional |
The #1 mistake teams make:
Skipping the "Use Case" field. Without understanding why a user needs a feature, you can't prioritize it against competing requests. Two requests might sound similar but serve completely different needs — the use case reveals the real priority.
6 Templates at a Glance
The 6 Templates — Detailed Guide
1. Simple Feature Request Form
Google Forms / Typeform
A lightweight form that captures the essentials: who's requesting, what they need, and why it matters. No overhead, no complexity. Share the link in your app, email signature, or support replies. Responses land in a spreadsheet you can sort and prioritize weekly.
Template Fields
- Requester name & email
- Feature title (one-line summary)
- Description (what should it do?)
- Use case (why do you need this?)
- Priority (nice-to-have / important / critical)
- Category (UX, integration, performance, new feature)
How to Use This Template
Create a Google Form with these fields. Share the link in your app's help menu, support email signatures, and onboarding emails. Review submissions weekly in the linked spreadsheet. Group similar requests and track vote counts manually.
Pros
- Zero cost — Google Forms is free
- Takes 5 minutes to set up
- Users are familiar with form interfaces
Cons
- No voting — you can't tell which requests are most popular
- Duplicate submissions pile up without deduplication
- Manual tracking in spreadsheets doesn't scale past 50 requests
2. Spreadsheet Tracker (Google Sheets / Excel)
Google Sheets / Microsoft Excel
A structured spreadsheet with columns for every data point you need to make prioritization decisions. Includes formula-ready columns for RICE scoring, status tracking, and vote counting. The spreadsheet is your single source of truth — paste in requests from support tickets, emails, and conversations.
Template Fields
- Request ID (auto-increment)
- Feature title
- Detailed description
- Requester (name, company, plan tier)
- Date submitted
- Category (bug fix, enhancement, new feature, integration)
- Priority (P0–P3 or custom scoring)
- RICE Score (Reach × Impact × Confidence ÷ Effort)
- Status (new, under review, planned, in progress, shipped, declined)
- Votes / request count (how many users asked for this)
- Notes / product team comments
- Target release (quarter or sprint)
How to Use This Template
Duplicate the template to your Google Drive. Set up data validation dropdowns for Status, Priority, and Category columns. Add conditional formatting to highlight high-priority items. Use the RICE score column to auto-rank features. Review the sheet in your weekly planning meeting.
Pros
- Full control over columns, formulas, and views
- Easy to share with stakeholders
- Built-in sorting, filtering, and pivot tables
Cons
- Gets messy fast — spreadsheets weren't designed for request management
- No user-facing submission — everything is manually entered
- Version control issues with multiple editors
3. Notion Feature Request Database
Notion
A Notion database with custom properties, multiple views (table, kanban, calendar), and rich-text descriptions. Each feature request is a page with space for detailed specs, discussion, and linked tasks. The kanban view gives you a visual pipeline from 'New' to 'Shipped'.
Template Fields
- Feature title (page title)
- Status (select: New → Under Review → Planned → In Progress → Shipped → Declined)
- Priority (select: Low / Medium / High / Critical)
- Category (multi-select: UX, Backend, Integration, Mobile, Performance)
- Requested by (person or text)
- Vote count (number — manually updated)
- Effort estimate (select: XS / S / M / L / XL)
- Impact (select: Low / Medium / High)
- Target quarter (select: Q1–Q4)
- Page body: detailed description, user stories, mockups, discussion
How to Use This Template
Duplicate the Notion template to your workspace. Create views: 'All Requests' (table), 'Prioritized' (kanban by status), 'By Category' (board grouped by category), and 'This Quarter' (filtered table). Share the database link with your team. For external submissions, pair with a form tool that pushes to Notion.
Pros
- Beautiful kanban and table views built in
- Rich pages for detailed specs and discussion
- Easily integrates with your existing Notion workspace
Cons
- No native voting — vote counts are manual
- Sharing with external users requires publishing (limited control)
- Gets slow with 500+ database entries
4. Jira Feature Request Issue Type
Jira / Atlassian
A custom Jira issue type specifically for feature requests, separate from bugs and tasks. Includes custom fields for business context (requester, use case, revenue impact) that engineers typically miss. Requests flow through a dedicated workflow: Submitted → Triaged → Accepted → Scheduled → Done.
Template Fields
- Summary (issue title)
- Issue type: Feature Request (custom type)
- Description (rich text with template)
- Reporter / Requester
- Customer name & plan tier (custom field)
- Use case / business justification (custom field)
- Priority (Jira priority: Highest → Lowest)
- Labels (feature area tags)
- Story points / effort estimate
- Fix version / target release
- Status workflow: Submitted → Triaged → Accepted → Scheduled → In Progress → Done
- Linked issues (related bugs, epics, or stories)
How to Use This Template
Create a custom issue type 'Feature Request' in your Jira project settings. Add custom fields for Customer Name, Plan Tier, and Business Justification. Set up a dedicated workflow with approval gates. Create a Jira filter for 'All open feature requests, sorted by priority' and share the dashboard with product managers.
Pros
- Lives alongside your engineering work — no context switching
- Powerful workflows, automations, and JQL queries
- Connects directly to sprints and releases
Cons
- Jira is complex — overkill for non-technical stakeholders
- Customers can't submit or vote on requests
- Licensing costs add up ($8.15+/user/month)
5. Linear Feature Request Label
Linear
A label-based system within Linear that tags issues as feature requests. Linear's speed and keyboard-first design make triaging fast. Create a custom view that filters for the 'Feature Request' label, grouped by priority. Requests sit alongside your regular issues and can be promoted to planned work with a status change.
Template Fields
- Issue title
- Label: Feature Request
- Description (Markdown with template)
- Priority (Urgent / High / Medium / Low / No priority)
- Status: Triage → Backlog → Todo → In Progress → Done
- Project (group by product area)
- Cycle / milestone assignment
- Subscriber list (who's watching this request)
How to Use This Template
Create a 'Feature Request' label in Linear. Set up an issue template with pre-filled sections: Problem, Proposed Solution, Use Case, and Impact. Create a custom view filtering by the Feature Request label, sorted by priority. Use Linear's triage workflow to review new requests weekly.
Pros
- Lightning-fast UI — triaging 50 requests takes minutes
- Clean Markdown descriptions and keyboard shortcuts
- Seamless promotion from request → planned issue → sprint work
Cons
- No external-facing submission — only team members can create issues
- No voting mechanism for users
- Feature requests get buried alongside bugs and tasks
6. Trello Feature Request Board
Trello
A dedicated Trello board with lists for each stage of the feature request lifecycle. Cards represent individual requests, with checklists for acceptance criteria, labels for categories, and a voting power-up for lightweight prioritization. Share the board publicly so customers can see what's planned.
Template Fields
- Card title (feature name)
- Description (what and why)
- Labels (category: UI, API, Integration, Performance)
- Checklist: acceptance criteria
- Custom field: requester name
- Custom field: request count / votes
- Due date (target ship date)
- Members (assigned PM / engineer)
- Lists: Ideas → Under Review → Planned → Building → Shipped
How to Use This Template
Create a board with five lists: Ideas, Under Review, Planned, Building, Shipped. Enable the Voting power-up for lightweight prioritization. Create a card template with pre-filled description sections. Share the board link publicly (read-only) so customers can see the pipeline. Drag cards through lists during sprint planning.
Pros
- Visual and intuitive — anyone can use it
- Free tier supports basic feature request tracking
- Public boards build transparency with customers
Cons
- Voting power-up is limited — one vote per member, no external votes
- Gets unwieldy with 100+ cards
- No built-in reporting or analytics
Why Feature Request Templates Break Down
Templates are a great starting point, but every team eventually hits the same walls. Here's what happens — and how to avoid it.
Duplicates pile up
Without deduplication, the same request appears 15 times across different submissions. You waste time merging and reconciling instead of building.
The fix:
A voting board consolidates duplicates automatically — users vote on existing requests instead of creating new ones.
No user-facing submission
Templates live in your internal tools. Customers can't submit requests directly, so everything gets funneled through support tickets and email — creating extra work for your team.
The fix:
A public feedback board lets customers submit and vote without going through your support team.
Vote counts are manual
In spreadsheets and Notion, someone has to manually count "how many people asked for this" by scanning support tickets and emails. This is tedious and always outdated.
The fix:
Dedicated voting tools track demand automatically — each user's vote is counted in real-time.
The feedback loop never closes
When you ship a requested feature, how do you notify everyone who asked for it? With templates, you'd need to manually email each requester. Most teams skip this step entirely.
The fix:
Tools like Features.Vote automatically notify voters when a feature ships, closing the loop and building loyalty.
Skip the Template — Use a Voting Board
A feature voting board replaces the template, the spreadsheet, and the manual vote counting — all in one tool.
2-minute setup
Create your board, share the link, and start collecting feature requests. No template configuration, no spreadsheet formulas, no Jira admin.
Users submit directly
Embed a widget in your app or share a public board URL. Customers submit requests and vote on ideas without going through your support team.
Auto-close the loop
When you ship a feature, mark it as done. Every user who voted gets notified automatically — building loyalty and encouraging more feedback.
Free plan available. No credit card required.
Template vs. Dedicated Tool
| Capability | Spreadsheet / Notion | Jira / Linear | Features.Vote |
|---|---|---|---|
| User-facing submission | - | - | |
| Built-in voting | - | - | |
| Automatic deduplication | - | - | |
| Status change notifications | - | ||
| Public roadmap | - | - | |
| Embeddable widget | - | - | |
| RICE / prioritization scoring | |||
| Free tier available | - | ||
| Setup time | 30 min | 2+ hrs | 2 min |
Feature Request Best Practices
Always capture the use case — "why" matters more than "what." A feature request without context is a guess, not a data point.
Track request count, not just requests. The difference between 1 user wanting CSV export and 40 users wanting it changes everything.
Set clear statuses and update them. Nothing kills user trust faster than a request sitting in "Under Review" for 6 months with no update.
Close the loop when you ship. Tell the people who asked for a feature that it's live. This single habit drives more repeat feedback than anything else.
Say no transparently. Declining a request with a reason ("doesn't align with our product direction this quarter") builds more trust than silence.
Review requests regularly — weekly or biweekly. A template nobody looks at is worse than no template at all.
"The easiest way to add feature voting to your app, it almost feels like it natively belongs to your application! "
Gabriel P.,
Founder at PullNotifier
Frequently Asked Questions
Still not convinced?
Here's a full price comparison with all top competitors
Is it lacking a feature you need?
Chances are, we're already working on it. Check our roadmap
Okay, okay! Sign me up!
Start building the right features today ⚡️