---
url: >-
  https://docs.corbitaltech.dev/products/feedback-flow/features/feature-requests/managing.md
---
# Managing Feature Requests

Admin guide for managing, organizing, and updating feature requests.

## Overview

As an admin, you have full control over feature requests across all boards, including editing, updating status, assigning to team members, and merging duplicates.

## Accessing Feature Requests

### View All Requests

Navigate to **Admin Dashboard → Feature Requests** to see all requests across all boards.

### View Board-Specific Requests

1. Click **Boards** in header (navigation)
2. Select a board
3. View requests for that board only

### Search and Filter

Use powerful filters to find specific requests:

**Filters:**

* Status (Open, Planned, In Progress, Completed)
* Board
* Vote count
* Comment count

![Admin Feature Requests](/products/feedback-flow/public/screenshots/feature-filter.png)

## Editing Feature Requests

### Update Details

Click on any feature request to edit:

**Editable fields:**

* Title
* Description
* Status
* Attechments
* Visibility (public/private)

![Edit Feature Request](/products/feedback-flow/public/screenshots/feature-edit.png)

## Status Management

### Change Status

Update request status as it progresses:

**Common statuses:**

* Under Review
* Planned
* In Progress
* Completed
* New (default)

**Status change triggers:**

* Email notification to request submitter
* Status badge update
* Roadmap update

## Moving Between Boards

Move feature requests to different boards:

1. Open feature request
2. Click **Move to Board**
3. Select destination board
4. Confirm move

**Note:** Votes, comments, and history are preserved.

![Merge Duplicates](/products/feedback-flow/public/screenshots/feature-merge.png)

### After Merging

**Parent request:**

* Receives combined vote count
* Retains all comments
* Shows merge history

**Duplicate requests:**

* Marked as "Merged"
* Hidden from public view (optional)
* Redirect to parent request
* Preserve complete history

### Merge Chain

View full merge history:

* See all merged requests
* Track merge relationships
* Unmerge if needed

## Visibility Controls

### Toggle Public/Private

Control who can see a feature request:

**Public:**

* Visible on board
* Searchable
* Votable
* Commentable

**Private:**

* Admin-only visibility
* Hidden from public board
* Still tracked internally

### Mark as Spam

Flag spam requests:

1. Open request
2. Click **Mark as Spam**
3. Request hidden from public
4. Can be reviewed/restored later

## Discussion Management

### Lock Comments

Prevent new comments on a request:

1. Toggle **Lock Discussion**
2. Existing comments remain
3. New comments blocked
4. Displays "Comments locked" message

**Use when:**

* Decision made, no further input needed
* Conversation became unproductive
* Request marked as duplicate

### Pin Comments

Highlight important comments:

1. Hover over comment
2. Click pin icon
3. Comment moves to top
4. Marked with pin badge

## Attachments

### View Attachments

All uploaded files visible in admin view.

### Add Attachments

Admins can add files to any request:

* Screenshots

### Remove Attachments on edit time

Delete inappropriate or outdated attachments.

## CSV Export/Import

### Export Feature Requests

Download all requests as CSV:

1. Navigate to board
2. Click **Export CSV**
3. Select fields to include
4. Download file

**Exported fields:**

* id, board_is, title, description ,status_id ,created_by

### Import Feature Requests

Bulk upload via CSV:

1. Download template CSV
2. Fill in data
3. Click **Import CSV**
4. Map columns
5. Validate and import

## Bulk Actions

Select multiple requests for batch operations:

**Available actions:**

* Delete

![Bulk Actions](/products/feedback-flow/public/screenshots/feature-bulk.png)

## Best Practices

### Regular Review

Schedule time to:

* Review new requests
* Update statuses
* Respond to comments
* Merge duplicates

### Clear Communication

When updating status:

* Add comment explaining decision
* Set realistic expectations
* Thank users for suggestions

### Prioritization

Consider when prioritizing:

* Vote count
* Business value
* Implementation effort
* Strategic fit
* User impact

### Transparency

Keep users informed:

* Regular status updates
* Roadmap visibility
* Completion notifications
* Implementation timelines

## Next Steps

* [Status & Workflow](/products/feedback-flow/features/feature-requests/workflow) - Status management details
* [Merging Duplicates](/products/feedback-flow/features/feature-requests/merging) - Advanced merge techniques