Allow merging duplicate feedback posts while preserving votes, comments, and subscribers

A few months ago, our team at Wowzers adopted Featurebase as the central place to collect customer feedback and feature requests from both customers and entertainers. It fit naturally into our product process because people could submit ideas, vote on existing requests, and follow updates without needing long email threads. Internally, it also gave us a much clearer picture of which requests were gaining momentum over time.

Current Workflow

As our feedback volume grew, we started seeing many requests that described the same underlying problem using different wording. Even when we shared links to existing suggestions, new submissions continued to appear. Our team regularly reviewed new posts, categorized them, and tried to keep the board organized so vote counts accurately reflected customer demand.

Why We Stopped Using Featurebase

The biggest issue for us was not having a practical way to merge duplicate requests into a single canonical post while keeping everything intact. Closing duplicates or redirecting users scattered votes, comments, and subscribers across multiple entries, making prioritization less reliable. Over time, maintaining the board became increasingly manual, and that eventually pushed us toward another feedback platform.

Feature Request

It would be extremely helpful if Featurebase supported true duplicate merging. Ideally, an admin could select two or more requests and merge them into one primary post while automatically transferring all votes, comments, attachments, subscribers, and status history. It would also be useful if anyone who previously followed a merged request continued receiving updates on the surviving post without needing to subscribe again. A small merge history visible to admins would also help with auditing.

Why We're Considering Returning

We've been following Featurebase's recent improvements, and the product has clearly matured. Many of the capabilities that were missing when we last evaluated it are now available, so we're seriously considering moving back if this remaining workflow can be addressed.

Expected Benefit

This would reduce administrative work, keep vote counts accurate, and make roadmaps easier to prioritize. It would also help any team managing an active public feedback board where similar ideas naturally get submitted multiple times as the user base grows.