What, where, how blocking
Bug reports you can reproduce
A reproducible report: what's broken in one line, what you were doing, what you expected, how much it blocks you and a screenshot.
The questions, one per screen
They're already written and every one is editable: text, type, order, whether it's required. Respondents see one at a time.
- 1
In una riga, cosa non funziona? *
Testo breve · required
- 2
Cosa stavi facendo quando è successo? *
Testo lungo · required
- 3
Cosa ti aspettavi che succedesse?
Testo lungo
- 4
Quanto ti blocca? *
Scelta singola · 3 options · required
- 5
Allega uno screenshot
Immagine
- 6
Dove ti aggiorniamo
Email
When to use it
«It doesn't work» is the most common report and the least useful. The three questions here — what you were doing, what you expected, how much it blocks you — are exactly what's needed to reproduce it and to decide the order.
Three things that help
- «How much does it block you» gives you priority without asking for it: nobody knows if it's a P1, everybody knows if they're stuck.
- Screenshot optional but asked for: whoever has one attaches it, and saves you the next exchange.
- Point the webhook at your tracker: the report becomes a ticket without anyone retyping it.