Merge duplicates

Use merge when requests mean the same thing. A duplicate does not need to use the exact same words. If two requests are really asking for the same outcome, merging them usually gives your team a cleaner queue and gives users a better single place to follow the discussion.

Start with the suggested matches. When you open the merge flow from a request, UserJot first shows suggested duplicates automatically. These suggestions are based on similarity, so the most likely matches appear before you type anything.

Use search when the suggestion list is not enough. If the request you want is not in the suggested list, start typing in the merge search. This switches to normal text search so you can find the right request by title or description.

Choose the canonical request carefully. The request you merge into becomes the main request that stays active. In most cases, the best target is the clearer request, the older request, or the one that already has the strongest discussion around it.

Know what gets merged. When you merge a duplicate into a main request, UserJot moves the duplicate's comments onto the main request and carries over distinct reactions so useful signal is not lost. If the same person already reacted on the main request, that reaction is not duplicated.

Know what does not get merged. The duplicate request is not deleted. It becomes a merged request linked to the main one. Request subscriptions are also not automatically moved over, so the main reason to merge is to unify discussion and signal, not to merge every relationship perfectly.

Review the result after merging. The merged request will show that it was merged into another request, and the main request will show which other requests were merged into it. This makes it easier for your team to keep the history understandable and undo the merge later if needed.