Do you measure browser bug report quality by field completion or time to first reproduction?

i've seen teams add more required fields when reports are vague, then wonder why non technical reporters still leave gaps. i'd baseline three things for two weeks: time until an engineer first reproduces the issue, number of clarification loops, and percentage of tickets returned for missing context. then simplify intake around the smallest executable path: starting page, last known good state, decisive action, expected versus actual, browser context, and the first visible contradiction. a bug report is useful when the receiver can reproduce or confidently isolate the missing state without another meeting. which metric changed your team's reporting process? submitted by /u/Prestigious-Way1525 [link] [comments]