Merge duplicates
Merging duplicates keeps votes, comments, and discussion focused on one canonical request instead of splitting demand across several posts.
What counts as a duplicate
Two requests are duplicates when they ask for the same customer outcome, even if they use different wording. Exact matching is less important than intent.
Do not merge requests that only sound related. If one request is a broad workflow and another is a narrow improvement, keep them separate or clarify the broader one first.
Choosing the canonical request
The surviving request should usually be the clearest request, the older request, or the one with the strongest discussion. After merging, edit the surviving title or description if needed so future visitors understand it quickly.
Step-by-step
- 1
Open the merge flow. Start from the request you believe is a duplicate.
- 2
Check suggested matches. Tembrio shows likely matches first so you can inspect probable duplicates before searching manually.
- 3
Search when needed. If the target is not suggested, search by title or description.
- 4
Pick the canonical post. Choose the post that should remain active and public.
- 5
Review what moves. Distinct votes and useful discussion should carry into the surviving request so demand is not lost.
- 6
Clean the surviving request. Make the final post title and description clear enough for the next customer to find and vote on.
Details to remember
- Merging is not just cleanup. It protects the signal behind customer demand.
- A duplicate can use different words and still mean the same thing.
- When unsure, keep posts separate until the customer outcome is clearer.