Yeah, sadly I fully understand Daniel. Public AH is a mess and I don’t see how this could be changed…
Most of developers never worked as QA. Many of them never participate in development in AAA engine. And their reports are simply unclear and messy. I don’t blame anyone, I started as QA at AAA game - I got trained to create awesome reports for developers. But most of people here (especially at indie studios) know very little about efficient bug reporting. It’s not enough to say “there’s bug, it looks like this”.
This is classic paradox of bug fixing.
If the bug report isn’t awesome and clear, you can’t say anything until you fixed the issue
- Developer can’t say too much about issue until he finds the cause… And usually he needs to sacrifice few hours of work to find it…
- But… when cause is found, very often it can be fixed instantly
Let’s look at this issue. I though I provided excellent repro. Nope…
So I took my time, created copy of the project. Removed most of the content, hunted down the proper repro. Provided minimized version of my project (just few files, not saying anything about actual project). It took me hours… but programmer got stable repro, required to properly analyze problem and test the fix.
I don’t know… maybe the best thing here would be to create some awesome (but easy to understand) guide for efficient bug reporting. The basic QA training.
Pin in to AH site, even force people to watch it (let’s say it’s youtube guide) before posting in Bug Reports section for the first time
Unity hired entire team of students to go through this enormous amount of reports, they got 5K reports every month.