Playbook · 6 min read
How to Merge Duplicate Requests Without Losing Credit
Combine duplicate requests into one record while keeping every voter and requester credited.
In short
A guide to merging duplicate feature requests without losing the people behind them. Identify true duplicates, choose a canonical record, merge so votes and requesters carry over, preserve lineage for the loop, and notify everyone affected. Done right, merging sharpens your demand signal instead of quietly deleting the contributors who asked.
Duplicate requests are inevitable. The same need arrives worded five different ways from five different customers. The wrong fix is to close four as duplicates, which deletes their votes and their requesters. Merging combines them into one record while keeping everyone credited.
This guide covers how to merge cleanly so your demand signal gets sharper, not weaker, and so every requester stays in the loop for when the work eventually ships.
1.Confirm they are truly duplicates
Two requests are duplicates only if solving one fully resolves the other. Surface-level keyword overlap is not enough. The trap is merging two requests that share words but describe different problems, which buries one of them. Compare the underlying need, not the title.
2.Choose the canonical record
Pick the request with the clearest problem statement and the most context as the survivor. It does not have to be the oldest or the most upvoted. A well-described record makes a better home for the combined feedback than a vague one with slightly more votes.
3.Merge so votes and requesters carry over
When you merge, every vote, comment, and requester from the absorbed items must move onto the canonical record. This is the whole point. If your process drops them, you are deleting demand and breaking the loop for those people. Verify the carry-over before you finish.
4.Preserve lineage for the loop
Keep a trace from each original request to the merged record. When the work ships, everyone who asked on any of the merged items should get notified. Lineage is what lets a single ship event close the loop for dozens of separate requesters at once.
5.Notify everyone affected
Tell the requesters that their separate asks have been combined into one tracked item, and point them to it. Silent merges feel like deletion. A short note that says we grouped your request with others and you will hear when it moves reassures rather than alarms.
6.Handle splits the same way
Sometimes one request actually contains two needs and should split rather than merge. Apply the same lineage rule in reverse: each resulting record keeps its share of the original requesters so nobody loses their place. Splits and merges are two sides of keeping credit intact.
Frequently asked questions
Why not just close duplicates?
Closing as duplicate typically discards the votes and requesters on the closed item. That understates real demand and leaves those people out of the loop forever. Merging keeps every contributor attached to one canonical record, so the signal stays accurate and the loop stays intact.
What if I merge two requests that turn out to be different?
If your platform preserves lineage, you can split them back apart and the original requesters follow their respective needs. This is why merging on a system that tracks lineage is safe, while a manual close-and-delete approach is not reversible.
Related
Turn your customers into your roadmap
Spin up an AI-moderated feedback forum, weight every request by real deal value, and keep each requester in the loop from idea to ship.