One thing I quickly noticed while running and maintaining my own projects is how fast incoming feedback gets messy. Getting user input is great, but when five different people ask for the exact same feature using slightly different wording, your backlog quickly gets cluttered and votes end up split across multiple posts.
Going through the inbox manually to search for existing requests takes too much time. At the same time, I needed a way for users (and myself) to attach screenshots when reporting a bug instead of just trying to explain it in text.
To solve this for my own workflow, I built duplicate detection, soft-linking, bulk actions, and file attachments directly into Pullwish's triage system, even using my own local Ollama model for triage and duplicate identification.
1. Spotting Duplicates with Similar-Count Badges
Instead of searching through the entire list to see if a feature or bug already exists, Pullwish now does this automatically in the triage inbox:
Similar-count badges: When new feedback arrives, an automated badge shows up if there are already similar items in the system based on title and content.
Type-aware matching: The matching logic prioritizes matching bugs with bugs and features with features, so you don't get bug reports mixed into your feature suggestions.
2. Soft-Linking vs. Full Merging
Sometimes two requests are identical, but other times they are just related. Merging everything into one item can sometimes delete useful context or specific use-cases that you actually want to keep (I found out the hard way).
Because of that, I created two ways to handle duplicates:
Soft-link: Lets you mark items as duplicates or related without touching the votes or comments. It keeps things linked together so you have the full picture without cluttering your board.
Full merge: When two requests are genuinely the exact same thing, a full merge moves all the votes, comments, and followers over to the main item in one go.
3. File and Screenshot Attachments (Up to 10 MB)
Trying to figure out a frontend bug from a one-line text description is painful. A screenshot makes it obvious in two seconds.
You and your users can now attach up to 5 files (up to 10 MB each) on both feature requests and bug reports:
Visual thumbnails: Images show up as thumbnails directly on the detail view for quick review.
Fast and reliable storage: Handled primarily via Cloudflare R2, with automatic fallback to Vercel Blob so it stays fast and doesn't drive up hosting costs.
4. Bulk Editing for Faster Cleanup
Opening every single item in a new tab just to change a status or clean out spam was taking too long, and I am too lazy. With bulk editing, you can select multiple features or bugs at once and update status, change priority, archive, or delete them in a single API call.
Making Feedback Actually Usable
The goal with Pullwish has always been to make running projects manageable for a solo builder without needing a bunch of separate tools. Having duplicate detection, file uploads, and quick bulk triage in the same dashboard as my error tracking and roadmaps makes staying on top of user requests way less stressful.
You can try out the new triage inbox and file uploads in your dashboard now!
AI Disclaimer: The experiences and concepts shared in this article are my own. To ensure the best reading experience, I collaborated with Gemini AI to proofread my original draft, refine the sentence structure, and correct grammatical errors. No content or history was artificially generated.