I'm not angry, though I am quite annoyed by the fact that by now at least 10 of my reports (that I took the time to write up and provide screenshots for), have basically been relegated to the trash without notification by a nonsensical system.
And it's almost impossible to keep track of them to bump or repost them because, oh the irony, the bug report system is bugged and looking up your own reports doesn't work.
This is not the point. Of course reports with more votes should be prioritised, but that doesn't mean reports that haven't seen any (developer) activity for a year should just be closed. The bug still exists, so the report should stay open until it has been investigated (which might be months from now, or never).cigma wrote: ↑22 April 2022, 09:43 But the resources are limited. And as it says on the page for reporting bugs: "note: reports with the most votes are investigated first". So as a developer, if you have only 10 hours to spend: Should you use them on a bug with 100 votes or a bug with 5 votes? That is all I wanted to point out.
Sadly, also some of the reports with the most votes seem not to make any progress...
In both of those cases, it is up to the developer to mark it as a duplicate, ask for more information or close it as "not a bug". Or just ignore it if there is no time to work on it, no one is forcing developers to click on them.cigma wrote: ↑22 April 2022, 09:43 But in some cases a bug CAN be fixed, even if no developer is working on it.
For example, there are a lot of duplicates in the bug database. It may happen, the developer was fixing bug #111, but your bug #222 about the same problem was not answered. (Handling duplicates is definitely a problem on BGA!)
It can be, the problem was caused on the side of the user (e. g. cache, cookies), so BGA couldn‘t help it anyway. And one day, the "bug" seems magically fixed.
Nobody is opposed to reporting bugs, so I'm not sure what you're arguing against here. You say reports should be automatically closed. I argue nothing is gained by having the system automatically close reports, quite the contrary.
Suppose a brave developer sets out to go fix some old games (it happened recently with Connect Four). He looks through some report pages and comes across Battle of LITS: "not much to do here; almost all closed, outdated reports". While in reality all of those bugs still exist and some are pretty impactful.
So, Hearts then. Plenty to do, luckily some reports got auto-closed! Except they would still have been at the bottom of the list anyway, so they aren't hindering anyone (and might still be valid).
Meanwhile, the people who reported them are irritated their reports got closed for no reason. Why bother reporting?
No gain, plenty of loss.