- Nov 5, 2013
- 917
- 1.135
'Tis cool, despite the efforts of many, duplicate bug reports will always happen. Just like poor quality reports. Since the issue has been noted by PDS, you only need ignore this report. Bumping it doesn't help.
Personally I think simply locking duplicate reports on known issues would go a long way. No need to even comment in the thread, just lock it. Make a sticky thread that says "My report was locked, Why?" and simply explain that if your report is locked it is a known issue or has been reported before. Although some bugs are known, there are some workarounds. If you require help in that respect or wish to discuss the bug please take it to the main forum - This is not a discussion sub-forum. The exception here is if the bug is still trying to be replicated in a manner to confirm an issue.
Either that or just put a pic of a troll in the thread. I know which one would be funnier.
The Downside to this is the QA guys/girls don't communicate with forum members as much. The upside is QA team spend less time answering the same bug, which means they have more time to replicate more difficult issues. There is also other things to be considered here like how to deal with mechanics questions, many reports are posted each week, which some community members help these people out. But once the answer has been supplied and the OP is satisifed there is no reason for any further posts, so locking after a while seems fine.
The constant "still happening in X.X.X" posts are far worse, in my opinion, than duplicate reports.
Now now children, play nice...
As has been mentioned, we are aware of the bug and it's reported in our internal database.
And about us not communicating with forum members as much.. I would say my inbox begs to differ
