Docs › Public Pages

Public Bug Tracker

Give players a public-facing view of known bugs and their status. Players can browse, search, and upvote bugs without needing a Bugnet account — keeping your community informed and reducing duplicate reports.

Setup

  1. Go to project Settings > Public Tracker
  2. Enable the public tracker
  3. Configure which information is visible to players

Configuration Options

  • Search — Enable or disable search functionality
  • Upvoting — Enable or disable player upvoting
  • Category filters — Show or hide category filter controls
  • Priority filters — Show or hide priority filter controls
  • Page title and description — Custom text displayed at the top of the tracker
  • Visible statuses — Choose which bug statuses appear (e.g., show open and in_progress, hide closed)

Public vs Private Bugs

  • Only bugs explicitly marked as public appear on the tracker
  • Private bugs (internal-only) are never shown to players
  • Toggle visibility per-bug from the dashboard bug detail view

Player Submissions

Players can submit new bug reports directly through the public tracker. These reports go through the same triage pipeline as SDK-submitted bugs. An optional player email field lets you send follow-up notifications when the bug is resolved.

API

HTTP
# Get public tracker settings
GET /api/projects/:slug/tracker

# Update public tracker settings
PUT /api/projects/:slug/tracker

Example request body for updating tracker settings:

JSON
{
  "enabled": true,
  "allow_search": true,
  "allow_voting": true,
  "show_categories": true,
  "title": "Known Issues"
}
HTTP
# Public bug list (no auth required)
GET /api/projects/:slug/public/bugs

# Public bug detail (no auth required)
GET /api/projects/:slug/public/bugs/:id

# Vote on a bug (no auth required)
POST /api/projects/:slug/public/bugs/:id/vote

Public Roadmap

Share your development roadmap with your player community. Display planned, in-progress, and completed features and fixes so players know what to expect next.

Setup

  1. Go to the Roadmap tab in your project dashboard
  2. Enable the public roadmap
  3. Configure display settings

Display Options

  • Layout modes — Board (kanban-style columns) or List view
  • Status mapping — Choose which statuses map to which columns
  • Upvote counts — Show or hide vote totals
  • Bug counts — Show or hide per-column counts
  • Filters — Enable category and priority filters

Customization

  • Accent color — Custom color for highlights and interactive elements
  • Page title and description — Custom header text
  • Custom CSS — Full CSS override for advanced styling control
  • Bug selection — Choose which bugs appear on the roadmap by status, label, or manual selection

API

HTTP
# Get roadmap settings
GET /api/projects/:slug/roadmap

# Update roadmap settings
PUT /api/projects/:slug/roadmap

Example request body for updating roadmap settings:

JSON
{
  "enabled": true,
  "layout": "board",
  "accent_color": "#E8624A",
  "show_votes": true,
  "show_counts": true
}

Changelogs

Keep players informed about updates, fixes, and new features. Create and publish changelog entries tied to your game versions so your community always knows what changed.

Creating Entries

  • Manual — Write changelog entries with a title, version, and rich text body
  • Auto-generate — Automatically create a changelog from all resolved bugs since the last entry

Each entry includes: title, version, body content, author, publish status (draft or published), and creation date.

Publishing

  • Entries start as drafts — preview before publishing
  • Published entries are visible on the public changelog page
  • Unpublish entries at any time to revert to draft status

Public Changelog

Players see a timeline of published changelog entries, sorted by date (newest first). The changelog is accessible at your project's public changelog URL and requires no authentication to view.

API

HTTP
# List published changelogs (public, no auth)
GET /api/projects/:slug/changelog/public

# List all changelogs (authenticated)
GET /api/projects/:slug/changelog

# Create changelog entry
POST /api/projects/:slug/changelog

# Update changelog entry
PUT /api/projects/:slug/changelog/:id

# Delete changelog entry
DELETE /api/projects/:slug/changelog/:id

# Auto-generate from resolved bugs
POST /api/projects/:slug/changelog/generate

Example request body for creating a changelog entry:

JSON
{
  "title": "v1.2.0 - Bug Fixes",
  "version": "1.2.0",
  "body": "Fixed crash on level 5...",
  "published": false
}

White-Label Branding

Customize the look and feel of all public-facing pages to match your game's brand. Every element — from colors to logos to CSS — can be tailored so the tracker, roadmap, and changelog feel like a natural part of your product.

Available Settings

  • Company name — Displayed in headers and footers
  • Logo URL — Your studio or game logo
  • Accent color — Primary color for buttons, links, and highlights
  • Background color — Page background
  • Text color — Primary text color
  • Support email — Displayed for player contact
  • Custom CSS — Full CSS override for advanced styling
  • Hide Bugnet badge — Remove the "Powered by Bugnet" branding (Studio plan and above)

SDK Branding

Branding settings are also available to SDKs via a public endpoint. The in-game bug report widget automatically picks up your branding colors so it matches your game's look without extra configuration.

HTTP
# Get public branding (no auth required)
GET /api/projects/:slug/branding/public

API

HTTP
# Get branding settings
GET /api/projects/:slug/branding

# Update branding settings
PUT /api/projects/:slug/branding

# Get public branding (no auth)
GET /api/projects/:slug/branding/public

Example request body for updating branding settings:

JSON
{
  "company_name": "Indie Studio",
  "accent_color": "#E8624A",
  "logo_url": "https://example.com/logo.png",
  "hide_badge": true,
  "custom_css": ".tracker-header { font-size: 24px; }"
}