Get the Details While the Reporter Is Still There

A vague complaint comes back with the questions that make it reproducible,
asked in the first minute, not after QA has given up on it.

Install Free on GitHub

🎁 Beta users (first 100 installs) receive 150 clarified issues a month, free during beta testing

-- beta seats remaining!

The QA Challenge

CUSTOMER: "Site is slow"
↓
SUPPORT: "We'll look into it"
↓
QA: "Can't reproduce"
↓
DEV: "Works on my machine"
↓
CUSTOMER: "Still slow" → Churn

The details were lost in translation.

WhatProblem for QA

REPORT:
"Site is slow"
↓
WhatProblem, within a minute:
"As I read it: something that used to be quick now is not. To make this reproducible:
Which page or action feels slow?
Roughly how long does it take, and since when?
What were you searching for, and about how many results come back?"
↓
REPLY:
"Product search. About 30 seconds, since yesterday. 'Blue widgets', usually 500 or so results, and it used to be instant."
↓
IN THE ISSUE NOW: Product search for "blue widgets", about 500 results

Since: yesterday
Actual: about 30 seconds
Expected: instant, as before
Still open: browser and account type, listed as questions

A report that already has the steps, the timing and the environment gets the restatement and no questions.

QA Superpowers

🔍 Reproduction steps asked for, never assumed
⏱️ How long, and since when, on the record
📝 Browser, version and platform asked for when they are missing
🎯 Expected and actual, separated
📊 A clarity score to sort the queue by

How It Fits Your Workflow

1
User reports issue in GitHub
2
WhatProblem restates it and asks what is missing, within a minute
3
The reporter answers while it is fresh
4
QA reads the restatement and the answers, not the whole thread
5
Fix ships faster

Better Bugs = Faster Fixes

Turn vague complaints into fixable issues.

Install Free on GitHub

🎁 Beta users (first 100 installs) receive 150 clarified issues a month, free during beta testing

-- beta seats remaining!