3 ms·
One pattern I've noticed that leads to low quality bug reports is that high quality bug reports take time, and bug reports, even if they're high quality, are of
by tgsovlerkhgsel 4y ago
One pattern I've noticed that leads to low quality bug reports is that high quality bug reports take time, and bug reports, even if they're high quality, are often ignored if they're not an absolutely critical issue.
After spending an hour of time writing the perfect bug report a couple of times, and each time receiving no reward (= fix), often not even seeing a sign that anyone looked at the report, this gets incredibly frustrating, and creates a temptation to not put in the effort anymore.
Which results in low quality bug reports, which exacerbates the issue (makes work harder for the maintainers, makes bugs less likely to get looked at/fixed, makes it more likely that the user encounters more such frustration).
I see the pattern, but I don't have a solution. One thing I've started to do is filing an initial low-quality bug report and offering to follow up (and actually doing it) once anyone shows any amount of interest, but that still leaves a crappy and non-actionable bug report.
- Jiro 4y ago>After spending an hour of time writing the perfect bug report a couple of times, and each time receiving no reward (= fix), Something that may be happening in that case is that the demand for making the bug report high quality is not sincere, but is just meant to kill it by filibuster. The developers won't fix the bug regardless, but by making it easy to say "you didn't follow all these steps in submitting the bug", they can put the blame on the user rather than just admitting they won't fix it.