eoc wrote:I'm aware of some of the shortcomings of the ticket that was created. However it's still an improvement over the previous situation (no report at all) and so I didn't like that the only apparent problem was the statement "It's not a bug" – despite the fact that we can include suggestions. This also goes to thank you for actually providing helpful criticism as opposed to a plain dismissal!
Yes, I said "I understand your reaction"
eoc wrote:I guess what one could propose here is the restriction "on table #" be lifted somewhat, since suggestions relating to one game in particular won't always be able to specify a table number just so they're linked to the correct game category. In this case it would've been possible (with additional work for the reporter and questionable benefit to readers)
Well there could be a way to link a report to a game without a table number, but that would need extra work on the tracker, and why? It's possible to use any table number of this game (not really difficult to find from the player game history) so it's actually always possible to link the report to the correct game category.
eoc wrote:– but I can imagine in other cases it gets more tough to find a table demonstrating the situation for which you have ideas on how to improve it.
Well if the table demonstrates the situation it's better (and should be possible because otherwise how did the player think of this suggestion?), but even if it's not the case, at least linking the report to a table puts it in the correct game category and notifies the correct developer. That's quite some benefit
eoc wrote:And since in a different context it has been pointed out to me that the bug tracker's usability is lessened due to lack of people helping, I'd like to volunteer for that kind of organizational work, such as opening a new issue in the correct categories and communicating in the now-obsolete report why that had happened.
Thanks! It's always great to get help to organize and qualify reports.