Feedback

Feedback is a system for collecting input from users, clients, and stakeholders through organized boards. It enables you to gather bug reports, feature ideas, and questions through public URLs while keeping everything organized by project.

What is Feedback?

Feedback represents structured input collected from people outside your team. Each feedback submission includes:

Unlike internal notes or tasks, feedback is designed for external collection. People can submit feedback through public URLs without needing an account.

Feedback vs Ideas

The platform has both a Feedback system and an Ideas system. Here's when to use each:

Feedback is optimized for collection from external parties. Ideas is optimized for internal evaluation and decision-making.

You can convert feedback into ideas if an external suggestion warrants deeper evaluation.

Feedback Boards

Feedback is organized into boards. Each project can have multiple boards for different purposes.

What is a Feedback Board?

A feedback board is a container for related feedback. Each board has:

Board Purposes

Categorize boards by their intended use:

Purpose is for your organization only and doesn't affect functionality.

Board Visibility

Control who can access your feedback boards:

• Public - Anyone with the link can view the board and submit feedback
• Private - Only team members can view and add feedback

When a board is public, a shareable URL is generated that you can send to users, embed in your product, or share on social media.

Board Lifecycle

Boards progress through lifecycle states:

Use Closed when you want to stop collecting feedback but still reference existing submissions. Use Archived when the board is no longer relevant.

Default Board

When you create a new project, a "General Feedback" board is automatically created and set to public. This ensures every project is ready to collect feedback immediately.

You can disable automatic board creation in project settings if you prefer to set up boards manually.

Feedback Types

Each feedback submission is categorized by type:

Types help you triage feedback quickly. Filter by type to focus on bugs during a bug-fix sprint or review ideas for roadmap planning.

Feedback Status

Feedback items have a simple two-state workflow:

• New - Unprocessed feedback requiring review
• Done - Feedback that has been addressed or acknowledged

When you mark feedback as Done, the submitter receives an email notification (if they provided contact information). This closes the feedback loop with your users.

Public Feedback Collection

Public boards enable anyone to submit feedback through a dedicated URL.

How It Works

1. You share the public feedback URL (e.g., yoursite.com/p/project-slug/board-slug)
2. Visitors see a simple form with title, description, and type fields
3. They submit feedback anonymously or with contact information
4. Submissions appear in your dashboard for review

Submitter Types

The system tracks three types of submitters:

For authenticated users, their account is linked automatically. For guests, you can optionally collect name and email for follow-up.

Contact Information

Guest submitters can provide optional contact information:

• Name - For addressing them in follow-ups
• Email - For sending notifications when feedback is marked done

Contact fields are optional to reduce friction. Users can also add contact information after submitting if they initially chose to remain anonymous.

Rate Limiting

Public feedback endpoints are rate limited to prevent abuse:

• 5 submissions per hour per IP address
• Applies to both guest and authenticated submissions
• Helps prevent spam and bot submissions

This limit applies per board, so legitimate users can submit to multiple boards.

GitHub Integration

Connect feedback to your development workflow by converting submissions to GitHub issues.

Converting Feedback to Issues

When feedback represents actionable work, convert it to a GitHub issue:

1. Open the feedback item
2. Click Convert to Issue
3. Select the target repository
4. Optionally edit the issue title and body
5. Create the issue

The feedback item is updated with a link to the created issue and automatically marked as Done.

Requirements

To convert feedback to GitHub issues:

• Your team must have a GitHub account connected
• The GitHub account needs repository access
• The target repository must be linked to the project

Activity Logging

All feedback operations are logged for auditing:

• Feedback submissions
• Status changes
• Conversions to GitHub issues
• Board creation, updates, and deletion

View the activity log in your team settings to track feedback history.

Best Practices

1. Use descriptive board names - Help users understand what kind of feedback you want
2. Write clear descriptions - Explain what feedback is helpful
3. Create purpose-specific boards - Separate beta feedback from general support
4. Review regularly - Process new feedback weekly to keep the queue manageable
5. Close the loop - Mark feedback as done to notify submitters
6. Convert actionable items - Move bugs and features to GitHub for tracking
7. Archive old boards - Keep your active boards focused and current

Related Concepts

• Projects - Feedback boards belong to projects
• Tasks & Notes - Internal task tracking
• Accounts & Teams - Team member roles and permissions

Next Steps

• How to Create a Feedback Board
• How to Share Your Feedback Link
• How to Manage Feedback
• How to Convert Feedback to GitHub Issues