Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.feedovate.com/llms.txt

Use this file to discover all available pages before exploring further.

Overview

Feedovate gives your team a complete system for capturing user feedback, organizing it into actionable insights, and driving it through your product workflow. Every piece of feedback has a full lifecycle — from submission to resolution.

Collecting Feedback

Feedback enters your system through multiple channels, giving both users and your team flexibility in how requests are captured.

Public Portal

Users submit feedback directly through your branded portal at your-slug.feedovate.com — either anonymously or authenticated

Admin-Created

Team members can create feedback entries from the admin dashboard on behalf of users or from internal conversations

Voting

Users upvote existing feedback to signal demand, surfacing the most requested items naturally
When your portal is set to anonymous mode, anyone can submit feedback without creating an account. This removes friction and maximizes participation — ideal for early-stage products or open communities.

Organizing Feedback

Structure is what transforms raw feedback into actionable intelligence. Feedovate provides multiple layers of organization to keep your backlog clean and navigable.

Boards & Tags

Boards

Top-level groupings that define the type or area of feedback. Users select a board when submitting, and your team can reassign as needed. Each feedback item belongs to exactly one board.

Tags

Flexible labels for cross-cutting concerns. Use tags for themes like “mobile”, “enterprise”, or “quick-win” that span multiple boards. Items can have multiple tags for granular filtering.

Custom Statuses

Define the exact workflow stages that feedback moves through in your organization. Every workspace can have its own status pipeline.
1

Open

New feedback lands here. It has been submitted but not yet reviewed by your team.
2

Under Review

Your team is evaluating the feedback, gathering context, and assessing feasibility.
3

Planned

The feedback has been accepted and added to your product roadmap.
4

In Progress

Active development is underway. Users following this item see real-time progress.
5

Completed

The feature or fix has shipped. The feedback loop is closed.
Custom statuses are fully configurable. Rename, reorder, add, or remove statuses in Workspace Settings → Statuses to match your team’s exact workflow.

Search & Filtering

Quickly find what you need across your entire feedback backlog with powerful search and filtering.
FilterDescription
StatusShow only feedback in specific workflow stages
BoardFilter by feedback board
TagsFilter by one or more tags
AssigneeShow items assigned to a specific team member
Time RangeNarrow results to a specific date window
SearchFull-text search across titles and descriptions
Combine multiple filters to create precise views — for example, all “Feature Request” items tagged “mobile” that are “Planned” and assigned to a specific engineer.

Managing Individual Feedback

Each feedback item is a rich object with its own detail view, supporting a full range of management actions.

Assignment & Ownership

Assign to Team Members

Route feedback to the right person. Assignees receive notifications and the item appears in their personal queue for focused triage.

Feedback Actions

When multiple users submit the same request, merge them into a single item. Votes from all merged entries are consolidated automatically, giving you an accurate picture of true demand. If you merge by mistake, you can unmerge to restore the original items.
Control whether feedback is public (visible on your portal) or internal (visible only to your team). Use internal visibility for sensitive requests, internal bugs, or items that are not yet ready for public discussion.
Move feedback through your custom status pipeline as work progresses. Status changes are reflected on the public portal, keeping users informed without any manual outreach.

Comments & Discussion

Every feedback item has a dedicated comment thread for discussion between your team and users.

Team & User Comments

Team members and portal users can participate in discussions. Use comments to ask clarifying questions, share updates, or provide context on decisions.

File Attachments

Attach screenshots, documents, or files to feedback items for additional context. Each feedback item supports up to 5 attachments.

Comment Controls

Enable comment approval to moderate user comments before they appear publicly. When enabled, new comments from portal users are held in a review queue until a team member approves them. Configure this in Workspace Settings → Portal to maintain a professional and on-topic discussion.

Voting & Prioritization

Voting is the engine that drives data-driven prioritization in Feedovate.

Users Upvote

Portal visitors upvote the feedback items they care about most. Each user gets one vote per item — a simple toggle on or off.

Votes Consolidate on Merge

When you merge duplicate feedback, votes from all source items are combined into the merged entry, preserving the true demand signal.

Priorities Emerge

Sort and filter by vote count to see what your users want most. The highest-voted items represent your strongest signals for what to build next.
Vote counts are visible on the public portal, giving users transparency into what the community is requesting and encouraging participation.

Feedback Lifecycle

Every feedback item follows a complete lifecycle from creation to resolution. Here is how the pieces fit together.
Feedback is submitted through the public portal or created by a team member. It enters the system with an initial status, board, and optional tags.

Best Practices

Triage Regularly

Review new feedback daily or weekly. Consistent triage prevents backlogs from growing out of control and keeps users engaged.

Merge Aggressively

Duplicate feedback fragments your vote data. Merge similar items early to maintain accurate demand signals across your backlog.

Use Internal Visibility

Not every piece of feedback belongs on the public portal. Keep sensitive or premature items internal until they are ready for public discussion.

Close the Loop

When feedback is resolved, update the status promptly. Users who feel heard become your strongest advocates and most loyal customers.