Feedjoltdocs
Workflow

Merging duplicates

How do I auto-merge duplicate feature requests? Auto-merge is opt-in and off by default. The workspace owner sets a 0.80–0.99 confidence threshold. Below it, Feedjolt only suggests.

Two posts saying the same thing fragment votes and split conversations. Merge them.

How do I auto-merge duplicate feature requests?

Auto-merge is opt-in and off by default. Only the workspace OWNER can turn it on and set the threshold. Advanced AI (including auto-merge) is on Startup and Scale (not Growth).

Open Dashboard → Settings (footer My Account menu). The Auto-merge duplicates card (kicker AI) is shown to the owner. Use Enable auto-merge. Set Confidence threshold between 0.80 and 0.99 (the slider shows 80%–99%). The default is 0.90. Click Save changes.

When a new post is created, a background duplicate-check job scores it against existing posts. If auto-merge is on and the AI confidence is at or above the threshold, Feedjolt merges the new post into the existing match. If confidence is below the threshold, Feedjolt only suggests the pair for a person to review.

The same card has Scope: Same board only (default) or Across all boards.

AI Insights lists stored suggestions for the selected window. Review merge opens the same confirm dialog as the board. Insights itself does not merge.

Auto-merges are written to the workspace Audit log as merge:auto with actor system. There is no separate auto-merge badge on the post.

How to merge

  1. Open the post you want to keep (the target). This usually has the better title or more votes.
  2. Open More actions and click Merge Post.
  3. In the dialog, search for the duplicate (the source). Stored suggestions appear first.
  4. Confirm.

What happens:

  • The source post redirects to the target. Old URLs still work.
  • Votes transfer. If a customer voted on both, the duplicate is deduped (one vote on the target).
  • Comments move under the target. They keep their original timestamps.
  • Subscribers of both posts now follow the target.
  • A post.merged notification can go to subscribers (email/Slack).
  • The target shows a Merged from list of source posts.

Picking the survivor

Pick the post with:

  • The clearer title. "Add dark mode" beats "would be neat to have a dark theme like figma".
  • More votes - fewer customer notifications about a missing post.
  • More body detail. You can always edit the survivor; less to lose.

When NOT to merge

  • Same general area, different specifics. "Dark mode" and "Sepia mode" sound similar; treat them as separate. Merging them frustrates the sepia-mode customer.
  • Same idea, different boards. Manual merge can cross boards. For auto-merge, keep Scope on Same board only unless you want the background job to search all boards.

Undoing a merge

On the target post, the Merged from list shows each merged source. OWNER and ADMIN can click Unmerge. This works for auto-merged posts too.

Unmerge clears the merge link and the source post reappears. Votes and comments stay on the target. The source comes back with 0 votes.

API access

Merging is API-accessible: POST /api/posts/{id}/merge with target_id in the body. See Public API.

On this page