Merge Duplicate Canny Posts with Their Votes
Open the duplicate and use the merge icon to combine it into the intended surviving post. Votes and comments move to that remaining post; merging does not email users.
Before you start: Use an Admin role with merge permission and compare the full requests. Similar titles alone do not establish that users want the same outcome.
Worked example: Export to CSV and Download reports as CSV may be duplicates. Export with custom access rules is a different requirement if its permission boundary changes what must be built.
Step-by-step guide
Compare the requests
Read both descriptions and comments. Write down the shared outcome and any requirement that would be lost by combining them.
Choose the surviving post
Prefer the post with the clearest scope and useful ongoing discussion. Keep a note of both original links for review.
Perform the merge
Use the merge icon in the top corner and select the destination. Check the direction before confirming so the intended public post remains.
Inspect the retained evidence
Open the surviving post, review the moved comments and voters, and check that distinct concerns are still understandable.
Review reversal limits
The merge is recorded in post comments, where Unmerge is available. Avoid a long chain of merges before checking each result.
Common mistakes
Merging related but different outcomes
Consolidating titles can erase a real permission or workflow distinction. Keep those requests separate and explain their relationship.
Sources and verification
Based on product documentation checked on 2026-11-04. This is a documentation-based guide, not a hands-on benchmark. Features and availability can change.