Bugscope

Who Bugscope is for

For testers whose bug reports keep coming back with "cannot reproduce", and for anyone who has argued about severity with a developer who had a different definition of critical. It handles both general software QA and free-to-play game QA, with severity language appropriate to each.

What Bugscope does

You describe what you saw and Bugscope structures it into a real report: reproduction steps, expected versus actual, environment, and a severity score derived from how often it happens and what it blocks. The score is transparent arithmetic rather than a model’s opinion — frequency multiplied by whether it blocks the user, whether data is lost, and whether it touches revenue — and it is always recomputed on the server, so a score cannot be edited into something more convenient. It also checks new reports against your existing ones for semantic duplicates.

• →General software QA and free-to-play game QA severity bands
• →Transparent, recomputed severity score — never a model’s guess
• →Semantic duplicate detection against your existing reports
• →Jira-compatible Markdown and JSON export

How Bugscope works

1. 01

   Describe what happened

   Rough notes are fine. The structure is what Bugscope adds.

2. 02

   Set frequency and impact

   How often it reproduces, whether it blocks the user, whether data is lost, whether it affects revenue.

3. 03

   Watch the severity update live

   The score recalculates in the browser as you fill the form, then is recomputed server-side so it cannot be tampered with.

4. 04

   Export the ticket

   Jira-compatible Markdown written to read like a real ticket, or clean JSON.

What Bugscope does not do

Bugscope does not file the ticket for you — there is no Jira, Linear or GitHub integration, so export is copy-and-paste by design. Duplicate detection needs an embedding model available locally and switches itself off quietly when there is not one, so treat it as a helpful check rather than a guarantee. The severity score is a heuristic about player or user impact; it does not know your release criteria, and it is meant to start the conversation about priority rather than end it.

Common questions

Works well with