Finding and merging duplicate Requests

Find duplicate Requests, merge them into one retained Request, and undo a merge when needed.

Written By Markus Palm

Last updated About 1 hour ago

Overview

Merge duplicate Requests to keep one Request for the same customer need. The Request you keep receives the Requesters and comments from the Requests merged into it.

Related feedback does not always need a merge. When it adds context to a different need, link it as an Insight instead.

Find duplicate Requests

Go to Requests & Insights → Requests and click 'Find duplicates' to review AI-detected candidates. Open the suggested Requests and compare the customer need before merging them.

You can also act on duplicate suggestions in Triage, or merge a duplicate you find while browsing Requests.

Note: AI Autopilot controls automatic handling of eligible matches.

Merge Requests

Choose the Request to keep

Keep the Request with the clearest description of the shared need. Check its category, visibility, status, and linked development work before you confirm the merge.

The confirmation lists the Requests under Merging and Keeping. Merging shows the Requests that are merged away and removed from public view; Keeping shows the Request that remains as the main record.

Merge from an open Request

  1. Open one of the Requests and open its 'Merge' menu

  2. Choose 'Merge other requests into this' to keep the open Request, or 'Merge into another request' to keep a different Request

  3. Search for and select the other Request or Requests

  4. Check the Merging and Keeping entries

  5. Click 'Merge requests'

When you review an AI-detected candidate, click 'Swap direction' in the confirmation to change which Request is kept.

Important: Read the Keeping entry before you confirm. Reversing a merge in the wrong direction means unmerging, which deletes any replies added to the merged thread.

Merge a selection

To combine several Requests from the list, select the specific rows, right-click one of them, and choose 'Merge' → 'Merge into another request', then select the Request to keep. The same Merging and Keeping check applies.

What happens after a merge

  • The retained Request stays active: The merged Requests are removed from public view

  • Requesters and comments move: The retained Request brings the demand and discussion together

  • The original Requests remain traceable: Merged content appears in the retained Request's Insights and activity

Tip: Review the retained Request's title, description, and status after the merge so they describe the combined need.

Unmerge a Request

Unmerging makes a merged Request separate again.

  1. Open the Request that contains the merged content

  2. Open 'Insights' and find the merged Request

  3. Open that item's 'More actions' menu

  4. Choose 'Unmerge request'

Featurebase removes the merged thread and the Requesters that the merge transferred from the retained Request. Requesters who were already on the retained Request stay there. Review both Requests and their discussions afterward.

Important: Replies added to the merged thread after the merge are deleted with it and are not moved back to the original Request. Copy any reply you want to keep before you unmerge.

FAQs