Feature Requests and Duplicate Review
Capture feature requests with business value and effort, then review suggested duplicate clusters before any votes are merged.
These images are illustrations of the concept, not screenshots of the actual product.
Overview
Feature Requests and Duplicate Review is where customer demand enters the PlanMagnet concept. It covers the list of feature requests across all products, the form for submitting a new request with business value and effort, and a review screen that proposes grouping requests that describe the same need. It lives under Products, next to Roadmaps and Releases, so the path from a request to a planned roadmap item stays inside one module.
Feature feedback arrives from many channels at once: sales calls, support tickets, surveys and direct submissions. The same need is often written four different ways, each collecting its own votes, while one loudly phrased request rises to the top of the list. Ranking on raw vote counts then rewards wording rather than real demand.
The illustrations trace the full path. The Features page summarizes total, in-progress and completed requests along with an average priority score, and lets a product manager filter by status, from submitted and under review through planned, in progress, completed, declined and duplicate, and sort by priority, votes or value. The New Feature form records a title, description, status, effort estimate and tags, followed by a Business Value section scored from 0 to 100. The duplicate review screen, labeled AI-assisted, shows a suggested cluster of related requests with their source, vote count and similarity score, compares the raw vote total with de-duplicated demand that counts each person once, and offers to merge the cluster into one renamed request or mark it as not duplicates.
The design keeps a person in charge of every merge: a notice states that the grouping is a proposal to review before merging. A side panel suggests linking the merged request to an existing roadmap item that already contains related epics, and another sets the cluster beside the loudest single request so its combined weight is easy to judge.
What this concept shows
- A feature request list with summary cards for total, in-progress and completed requests and an average priority score
- Status filters for submitted, under review, planned, in progress, completed, declined and duplicate requests
- Sorting by priority, votes or business value
- A New Feature form with status, effort estimate, comma-separated tags and a 0 to 100 business value score
- Suggested duplicate clusters showing each request's source channel, vote count and similarity score
- A raw vote total set against de-duplicated demand that counts each voter once
- A merge target with an optional rename, plus Merge and Not duplicates actions
- A suggested link from the merged request to an existing roadmap item, with Dismiss and Link options
How it works
- Open Features under Products to see request totals and filter the list by status.
- Choose New Feature and enter a title, description, status, effort estimate, tags and a business value score.
- Open Duplicate review, filtered to open requests and sorted by de-duplicated demand.
- Check the requests in the suggested cluster and compare the raw vote total with de-duplicated demand.
- Pick a merge target and name, then merge the requests or mark them as not duplicates.
- Link the merged request to the suggested roadmap item, or dismiss the suggestion.
Who it's for
- Product managers
- Customer success and support leads
- Sales engineers who relay customer requests
- Product operations teams
Illustrations
3 illustrations of this concept. Select one to view it full size.
Feature Requests List
The Features page gathers feature requests across all products, with a count under the heading and a New Feature button at the top right. Four summary cards show total features, those in progress, those completed and the average priority score. Beneath them, a filter row offers status chips (All, Submitted, Under Review, Planned, In Progress, Completed, Declined and Duplicate), and on the right a sort control switches between Priority, Votes and Value, with Priority selected. This illustration shows the empty state, with a message that no features match the selected filters. Including a Duplicate status and a value-based sort signals that the design treats triage and prioritization as part of the list itself rather than a separate spreadsheet. Features is highlighted under Products in the sidebar.
New Feature Request Form
The New Feature form is introduced as a way to define a feature request with business value metrics. A Feature Details card holds a Title field with an example search feature as placeholder text, a Description area asking for the feature and its user value, dropdowns for Status (defaulting to Submitted) and Effort Estimate (defaulting to Medium), and a Tags field that takes comma-separated values. A second card, Business Value, begins below with a numeric score on a 0 to 100 scale, prefilled at the midpoint, and helper text asking how much value the feature delivers. Cancel and Create Feature buttons sit at the top, with the create button shown in a muted state while the form is blank. Pairing value with effort is designed to give the request list its priority inputs.
AI-Assisted Duplicate Review
This illustration shows the duplicate review step, reached from Products, Features and then Duplicate review, filtered to open requests and sorted by de-duplicated demand. A heading labeled AI-assisted introduces a suggested cluster, with a notice that the grouping is a proposal to review before merging and that votes are consolidated per person. The cluster card, about enterprise identity-provider sign-in in the sample data, lists four checked requests, each with its source channel (a sales call, support ticket, survey or direct submission), a vote count and a similarity bar with its score. A summary strikes through the raw vote total, shows the lower de-duplicated demand and notes how many people voted on more than one request. A merge-target dropdown with a rename sits beside Not duplicates and Merge buttons. On the right, one panel suggests linking to an existing roadmap item, with Dismiss and Link, and another compares the loudest single request.
Topics
- feature request management
- feature voting
- customer feedback deduplication
- merge duplicate feature requests
- feature prioritization
- business value scoring
- product feedback tool
- feedback triage
- AI duplicate detection
- feature request tracker
Related concepts
Product Roadmaps and Releases
A product portfolio with roadmaps filtered by type and visibility, and releases tracked from draft through to released.
4 illustrations
Task Board and AI Work Breakdown
The board where work moves, the form that adds to it, and an assisted breakdown that turns a paragraph of intent into reviewable work items.
3 illustrations
Project Portfolio and Milestones
A portfolio view that runs from every project, to the ones in flight, to the milestones they are judged by — plus a form to start the next.
4 illustrations