Forum:How would you rate the support you received?

"'How would you rate the support you received?'"

How do you reply to this question? I've gotten this email a bunch of times now and I never know how to react. Sure, the support people are friendly and they get back to you relatively quickly and that's good and all. But what about the bug I reported? It's nice to hear things like:

"'We appreciate you letting us know about this problem with the API. That definitely is not working as intended. I will pass your report directly to our technical staff for investigation and review.'"

But what does that tell me? Will the bug get fixed? And if so when? And shouldn't they ask me what I think of their support after those other question have been answered?

So which is it? "Good, I'm satisfied" or "Bad, I'm unsatisfied"? For me it's neither at this point. The bug still exists after all... --
 * Really a matter of opinion, if you feel any sign if negative means, then mark it bad, you feel it is all good, mark it good. Click the box that you think is necessary. -- 13:13, July 21, 2012 (UTC)
 * Pecoes, you gave them info on the bug. They'll need to use that info to detect in which file it is, what it is like etc. Wikia's codebase is enormous, please be patient. :) TK-999 (talk) 13:17, July 21, 2012 (UTC)


 * Sure. I'm patient. Fixing bugs can take a bit of time. I know that. But the mail asking me what I think of their support arrived now. They most likely haven't even begun to look at this bug - it's the weekend after all - but they already want to know what I think of their support. That's what puzzles me. --

It might also be automatically sent. For me, they also arrive after I receive an official response. TK-999 (talk) 13:36, July 21, 2012 (UTC)
 * Yes, I suspect as much. Well, I replied with "Good, I'm satisfied." now. Not because I'm satisfied - nothing has happened yet - but because it's far too early to say otherwise. But still: This is awkward. --
 * I think it's annoying that we hear that the bug has been passed onto the technical team, then hear no more. It's impossible to know if the bug is taking time to fix or they've just forgotten about it, or they think they've fixed it but actually haven't-- Category:Acer4666 16:32, July 21, 2012 (UTC)
 * I'm starting to think Wikia needs a public bug tracker. Just a few days ago I wrote in another forum that would be overkill, but I've changed my mind. Some clarity and transparency would be helpful. What bugs are there? What's their priority? Have they been assigned? Have they been fixed? Will they be fixed? What bugs have been classified as bogus? Among other benefits this would also remove a major source of tension between Staff and users. --


 * I've been thinking about that myself but figured it might actually cause additional tension between staff and users due to, for example: under-prioritizing bugs (why does my important bug report have such a low priority?), the time it takes for some bugs to get fixed, closing or dismissing bug reports that describe unreproducible issues (why did they close my ticket even though I still see the issue?).


 * Technical Update blog posts usually contain a description of the most prominent bugs, so as soon as they are back up again, we'll be able to tell if the big issues are being solved. — Sovq 06:50, July 22, 2012 (UTC)