Reports

Bug reports are the core of Forge Logger. They are submitted by game plugins via the Ingest API and appear in the dashboard for review, triage, and export.

Report list

Navigate to Reports to see all bug reports across your projects. Each report shows:

• Title and description
• Severity — low, medium, high, or critical
• Status — new, triaged, in_progress, resolved, export_pending, exported, duplicate, suspected_duplicate, wontfix, or closed
• Reporter type — player, tester, qa, internal, or system
• Environment and build version tags
• Attachment count and event count
• Export status — whether the report has been exported to GitHub, GitLab, Jira, Discord, or Webhook

You can also view reports scoped to a single project from the project page.

Report detail

Click a report to see the full detail view:

Context

If the plugin submitted game context, you will see:

• Scene name and checkpoint
• Platform and build version
• Locale
• Player position (3D coordinates)
• Performance metrics (FPS, frame time, memory)
• Custom extra data

Attachments

Screenshots, videos, log bundles, and save states attached to the report. Click to view or download.

Events

Telemetry events linked to the report — either submitted inline with the report or referenced by event ID. Events show the type, timestamp, and payload.

AI Summary

If the project has AI Summary enabled, the report includes:

• Summary — AI-generated description of the issue
• Reproduction steps — step-by-step instructions to reproduce the bug
• Confidence — how confident the AI is in its analysis (0-1)
• Generated at — timestamp of the analysis

Click Regenerate to re-run the AI analysis if the summary is outdated or inaccurate.

Deduplication

If AI Deduplication is enabled and the report was identified as a duplicate:

• The report status is set to duplicate
• A link to the root report is shown
• The root report displays the total occurrence count

Exporting a report

From the report detail page, click Export and select a provider:

• GitHub — creates a GitHub Issue
• GitLab — creates a GitLab Issue
• Jira — creates a Jira ticket
• Discord — sends a notification to a Discord channel
• Webhook — sends a POST request to a configured URL

The integration must be configured on the project first. See Integrations.

After a successful export, the report’s export entry for that provider is marked success and, when the provider returns one, the external issue/ticket URL is linked from the report. Exporting does not change the report’s own status.

Report statuses