Skip to main content
Organization

Bulk editing Requests

Select several Requests in the Requests list and apply one change to all of them.

Written By Markus Palm

Last updated About 3 hours ago

Overview

Bulk editing applies the same change to selected Requests. Use it to assign work, update organization or planning fields, or clean up a set of Requests without opening each one.

Start with a filtered Request view so you can check which Requests the change should affect. Available actions depend on your permissions and the selection.

Select Requests

Select individual rows or a range

Open Requests & Insights → Requests and select Requests with the checkboxes. To select a range, select the first Request, hold Shift, and select the last Request in the range.

Right-click a selected Request to open the bulk action menu.

Select all matching results

After selecting a Request, click 'Select all' in the bulk-edit banner. The button shows the number of matching Requests when available.

Select all includes every Request matching the current list, not just the rows loaded on screen. If status groups are hidden, show all status groups before using Select all. Use 'Unselect all' to clear the selection. Changing the filters or switching views also clears it.

Important: Review the count and the active filters before you apply a change. A bulk action applies to every selected Request, including rows you have not scrolled to.

Apply a bulk change

  1. Right-click one of the selected Requests

  2. Choose the property or action from the menu

  3. Select the new value or complete the action's controls

  4. Review and confirm the scope if a confirmation appears

  5. Wait for the result and check the updated Requests

The menu can include:

  • Organization: Status, assignee, category, labels, and form fields

  • Planning: ETA, value, and effort when value and effort prioritization is enabled

  • Attribution and access: Author and Request visibility

  • Review and cleanup: Approval or rejection, merging, copying, and deletion where available

One bulk action covers up to 5,000 Requests. Changing the author or deleting covers up to 1,000. When the selection is larger, Featurebase rejects the action and asks you to narrow the filter.

Note: Changes to category, author, or visibility can affect who sees a Request. Review those changes against your access rules.

Merge or delete a selection

To merge Requests, select the specific rows and use 'Merge'. Follow the merge guide to choose which Request to keep.

For deletion, choose 'Delete' and read the confirmation carefully. Use the count to confirm that the selection matches your intent.

Important: Deleting removes the selected Request records. To consolidate duplicate feedback while keeping its demand and discussion, merge the Requests instead.

FAQs

A merge needs an explicit set of Requests, so it is only available when you select specific rows. Select all describes the selection by its filters rather than by individual Requests. Clear the selection, select the rows you want to merge, then use 'Merge'.

If the message says that only some of the selected Requests were updated or deleted, review the affected Requests before selecting the remaining work and trying again.

If the message says the server did not confirm the change, the change may still have applied. Refresh the list and check the result before you retry, so you do not apply the change twice.

A Request leaves the current view when it no longer matches the view's filters. For example, assigning a Request removes it from a view filtered to unassigned Requests. The change succeeded; open the Request from another view or search to confirm it.

Still need help? Ask the team