Docs
Docs

Managing Feedback

Learn how to effectively manage bug reports, engage with your community, and handle releases.

Working with Bug Reports

You will be notified of each bug reported by users depending on your settings. You will always see a notification on the site, and may receive notifications via Discord bot and email.

AI-Powered Bug Processing

Depending on your AI submission verification level settings, artificial intelligence will:

  • Make sure the submission is detailed enough
  • Ensure it covers only one bug
  • Check for duplicates in the system
  • Assign appropriate tags and priority

You can customize these settings in ‘Settings / General’ under Bug Description Validation Level:

  • AI Check - The AI evaluates and alerts if description is invalid
  • Minimum Character Limit - Ensures descriptions are at least 50 characters
  • No Check - Omits validation

Managing Individual Bug Reports

For each bug report, you can:

  • Delete the submission
  • Change status (New, In Progress, Resolved, etc.)
  • Start discussions in the comments section
  • Ask for more information from the reporter

Requesting Additional Information

BetaHub makes it easy to request more details from testers. For any bug report element (steps to reproduce, screenshots, videos, logs), you’ll see an Ask for [Something] button.

Clicking this button will cause BetaHub to contact the reporter (often via Discord bot) and request specific additions to the report.

Bug Report Lifecycle

A reported bug receives a New or Duplicate status initially. In BetaHub, duplicates are positive! Each duplicate elevates the original bug report’s priority, increasing chances of resolution.

The lifecycle typically follows:

  1. New - Just reported
  2. In Progress - Being worked on
  3. Resolved - Fixed and ready for testing
  4. Closed - Verified as fixed

Community Engagement

Communication Best Practices

  • Respond promptly to bug reports to keep testers engaged
  • Provide updates on bug status to maintain transparency
  • Thank contributors for detailed reports
  • Use the commenting system for discussions

Managing Tester Expectations

  • Set clear expectations about response times
  • Explain your bug triage process
  • Communicate release schedules
  • Acknowledge valuable contributions

Release Management

Creating Releases

Releases are essential for:

  • Associating bugs with specific versions
  • Communicating updates to your community
  • Tracking progress over time

To create a release:

  1. Go to your project page
  2. Click New Release
  3. Fill in release details:
    • Label - Version identifier
    • Description - What’s new (supports Markdown)
    • Images - Screenshots or promotional images

Release Distribution

When you publish a release:

  • It appears on your project page
  • Email notifications are sent to subscribers
  • Discord announcements are posted (if integrated)
  • Images are shared according to your settings

You can edit releases after creation. Discord messages will automatically update to reflect changes.

Advanced Management Features

Duplicate Detection

BetaHub’s AI automatically identifies potential duplicates. When duplicates are found:

  • The new report is marked as duplicate
  • The original report’s “heat” increases
  • You can merge or separate reports as needed

Bulk Operations

For managing multiple reports:

  • Filter by status, priority, or tags
  • Perform bulk status changes
  • Export reports for external analysis

Analytics and Insights

Monitor your project’s health through:

  • Bug report trends
  • Tester engagement metrics
  • Release feedback patterns
  • Community sentiment analysis

Integration with External Tools

Send bug reports to your preferred project management tools:

  1. From List View: Click three-dots menu (…) → Send to…
  2. From Detail View: Click three-dots menu in report → Send to…

Supported integrations include Jira, Asana, GitHub, Notion, and Monday.com.

Best Practices

Bug Report Management

  • Triage regularly - Review new reports daily
  • Prioritize effectively - Use BetaHub’s priority system
  • Communicate status - Keep reporters updated
  • Document solutions - Add resolution notes

Community Building

  • Engage positively - Thank contributors
  • Be transparent - Share development progress
  • Provide feedback - Let testers know their impact
  • Recognize contributors - Highlight valuable testers

Process Optimization

  • Review regularly - Assess your workflow efficiency
  • Automate where possible - Use integrations and AI features
  • Gather feedback - Ask testers about their experience
  • Iterate and improve - Refine your process over time

Getting Help

If you need assistance with managing feedback:

  • Join our Discord server for community support
  • Check the FAQ for common questions
  • Contact support for technical issues

Next Steps

Managing Feedback

Learn how to effectively manage bug reports, engage with your community, and handle releases.

Working with Bug Reports

You will be notified of each bug reported by users depending on your settings. You will always see a notification on the site, and may receive notifications via Discord bot and email.

AI-Powered Bug Processing

Depending on your AI submission verification level settings, artificial intelligence will:

  • Make sure the submission is detailed enough
  • Ensure it covers only one bug
  • Check for duplicates in the system
  • Assign appropriate tags and priority

You can customize these settings in ‘Settings / General’ under Bug Description Validation Level:

  • AI Check - The AI evaluates and alerts if description is invalid
  • Minimum Character Limit - Ensures descriptions are at least 50 characters
  • No Check - Omits validation

Managing Individual Bug Reports

For each bug report, you can:

  • Delete the submission
  • Change status (New, In Progress, Resolved, etc.)
  • Start discussions in the comments section
  • Ask for more information from the reporter

Requesting Additional Information

BetaHub makes it easy to request more details from testers. For any bug report element (steps to reproduce, screenshots, videos, logs), you’ll see an Ask for [Something] button.

Clicking this button will cause BetaHub to contact the reporter (often via Discord bot) and request specific additions to the report.

Bug Report Lifecycle

A reported bug receives a New or Duplicate status initially. In BetaHub, duplicates are positive! Each duplicate elevates the original bug report’s priority, increasing chances of resolution.

The lifecycle typically follows:

  1. New - Just reported
  2. In Progress - Being worked on
  3. Resolved - Fixed and ready for testing
  4. Closed - Verified as fixed

Community Engagement

Communication Best Practices

  • Respond promptly to bug reports to keep testers engaged
  • Provide updates on bug status to maintain transparency
  • Thank contributors for detailed reports
  • Use the commenting system for discussions

Managing Tester Expectations

  • Set clear expectations about response times
  • Explain your bug triage process
  • Communicate release schedules
  • Acknowledge valuable contributions

Release Management

Creating Releases

Releases are essential for:

  • Associating bugs with specific versions
  • Communicating updates to your community
  • Tracking progress over time

To create a release:

  1. Go to your project page
  2. Click New Release
  3. Fill in release details:
    • Label - Version identifier
    • Description - What’s new (supports Markdown)
    • Images - Screenshots or promotional images

Release Distribution

When you publish a release:

  • It appears on your project page
  • Email notifications are sent to subscribers
  • Discord announcements are posted (if integrated)
  • Images are shared according to your settings

You can edit releases after creation. Discord messages will automatically update to reflect changes.

Advanced Management Features

Duplicate Detection

BetaHub’s AI automatically identifies potential duplicates. When duplicates are found:

  • The new report is marked as duplicate
  • The original report’s “heat” increases
  • You can merge or separate reports as needed

Bulk Operations

For managing multiple reports:

  • Filter by status, priority, or tags
  • Perform bulk status changes
  • Export reports for external analysis

Analytics and Insights

Monitor your project’s health through:

  • Bug report trends
  • Tester engagement metrics
  • Release feedback patterns
  • Community sentiment analysis

Integration with External Tools

Send bug reports to your preferred project management tools:

  1. From List View: Click three-dots menu (…) → Send to…
  2. From Detail View: Click three-dots menu in report → Send to…

Supported integrations include Jira, Asana, GitHub, Notion, and Monday.com.

Best Practices

Bug Report Management

  • Triage regularly - Review new reports daily
  • Prioritize effectively - Use BetaHub’s priority system
  • Communicate status - Keep reporters updated
  • Document solutions - Add resolution notes

Community Building

  • Engage positively - Thank contributors
  • Be transparent - Share development progress
  • Provide feedback - Let testers know their impact
  • Recognize contributors - Highlight valuable testers

Process Optimization

  • Review regularly - Assess your workflow efficiency
  • Automate where possible - Use integrations and AI features
  • Gather feedback - Ask testers about their experience
  • Iterate and improve - Refine your process over time

Getting Help

If you need assistance with managing feedback:

  • Join our Discord server for community support
  • Check the FAQ for common questions
  • Contact support for technical issues

Next Steps

On This Page