I'm sorry Paul. I have reported at least 6 bugs in the past in the issue tracker, never got so much as an automatic followup message.... it's unreasonable to use that system for the amount of bugs we can gather in a short time (there's just too much polishing to do in the game, just look at the amount of inconsistencies I've gathered while not even looking for them !!!). I will keep using the issue tracker for bugs that are gamebreaking and have weird patterns.
As a player... As a community, we would like to know what is not working properly without having to research the tracker for individual posts. More than that... how can we workaround those many bugs and keep playing while the team manage to fix stuff ? You guys never cover that part.... acknowledging it's a bug is where your role seems to stop... it's not enough.
If you read my long report (your last comment suggests you did not), I've put Issue trackers in the list of buggy things.... so.... you are free to refuse 1 day QC work from some1 with programming experience, or you can test the issue tracker and measure how long such a report would take to transfer.
Your job is not easy. I know it's your job to repeat ad nauseaum to use the issue tracker. Chante has acknoledged you were discussing improvements.
Here are some suggestions for the faster and least painful implementation :
Completly seperate the collection from the display of bugs...
Collection should be as fast and immediate as possible, encourage the use of quick lists and keywords. Display need to be clustered and consolidated.
Input - data collection:
-Ingame data collection (Implement a button ingame for screencap + bug report). You can recycle the 'Create Blueprint' interface, change the pipes so information goes frontier with title, game log/file, comment and capscreen. Tags can be the reproductibility and redundancy information.
- Add info for priority/gamebreaking - level of annoyance
- Automatic semantic clustering inhouse (DNN open source exist on the market, there's no need to create one.)
Output - feedback:
- Auto-message user when bug is confirmed + if ingame workaround is found + if bug is fixed.
Display on website :
- Consolidated list of all reported bugs with generic description of a good langage quality - (aka: ready for automatic translation)
- Include ingame workaround as soon as one is found.
- Publish stats for 'bug loads' on the site
Forum:
- Maintain a discussion on the forum for the weirdest and most resilient bugs so peeps can talk and experiment.
- Acknoledge those discussions when they happen on their own (it means it's a priority for players and they are unsatisfied from the feedback they got).