xander wrote:Meeeps wrote:Well, I fear the bug tracker became unusable, there are so many open tickets, many simply look invalid. I don't think it makes any sense anymore to post bugs there. It got no attention by devs. 2 tickets were resolved since june.
The fact that many of the tickets are useless is a result of the lack of moderation. The tracker moderators have vanished, and IV has not appointed anyone to replace them. Yet another reason to object to the existence of a publicly facing tracker in the first place---though I acknowledge that I lost that battle a long time ago.
That being said, the fact that only two tickets have been closed in the last several months does not imply that the devs do not check the tracker. They simply have not been focusing on bugfixing.
xander
Agree about the moderation, but I still think the situation could be turned around. I must admit that I was impressed when I came on-board the Alpha that IV had deployed a bug tracker. I've seen too many botched efforts of tracking bugs in anything but a bug tracker, including forums. While the current state of the tracker isn't much improvement, the potential is there.
I've used multiple trackers in the past with success, keeping one as public (essentially what we have now), and another that moderators can pull the public artifacts into (via a move operation). This latter tracker is "clean" in the sense that it provides a more tightly controlled list for the developers to work towards. If the permissions administration allows it, I'd allow anyone to comment on artifacts within this "clean" tracker, but not open new artifacts. This would allow consolidation of all the relevant information on a particular bug and be another line of defense against duplicates. Moderation of the public tracker could continue linking the constant stream of duplicates to the one artifact that was moved into the "clean" tracker. Reporters of the now-identified duplicate reports would then see where to post their information. The developers would also have the public tracker as reference if they're interested in the raw data and reports coming in from the community, so no information is ever lost.