More then 10 years I have been providing unix and linux support to internal and external clients.
I have probably implemented, evaluated and used more bugtracking and ticketing systems then a lot of you combined.
Here I am a user.. not an admin, nor the helpdesk, 2e or 3e line support person.
I choose not to use your bugtracker, because it is a waste of my time.
What you guys use for your internal kitchen, is your business. not mine.
No offense guys, but we shouldn't be forced to use your software to log bugs.
EDIT: come to think of it, you are actually the very first company I have ever come across that expects its
clients to use a bugtracker. Most take their clients feedback and log tickets themselves.
If you ask me, that's the way it should be used.
Hi1674 how about using the bug tracker to explain the issue you are having instead of expecting they have mind reading powers and just '' fix '' what ever it is that your whining about....
PvP has been addressed by the customers MANY MANY times.
They KNOW the problems but they seem to ignore the PvP feature.
hi1674 said:They KNOW the problems but they seem to ignore the PvP feature.
ofc notbut they seem to ignore the PvP feature.
peumer said:i restart hb but doesn't change is hole time this
ofc not
we are working on new bugreports for pvp atm
EDIT: come to think of it, you are actually the very first company I have ever come across that expects its
clients to use a bugtracker. Most take their clients feedback and log tickets themselves.
If you ask me, that's the way it should be used.
If Honorbuddy was running and this is a result of your restarting it, you might need to open Task Manager and make sure there isn't a stray, invisible Honorbuddy still running in the background.
Other than that, this Wiki page...
should help.
cheers,
CJ
Since english is not my native language i picked a bad word here..
Ignore should've been something like " not high in priority"
I notice there is now a paid plugins key, I am buddy lifetime user, is this key relevant to lifetime users?
Alright, to the tech support/coders/anyone who has anything to say about bugtracker and bug reports. Honorbuddy is a community driven bot, they do not have the manpower to beta test every single function of the bot and find all of the bugs themselves. This is why major companies (Such as Microsoft/Redhat/Bungie/TreyArch/InfinityWard/ (The list is endless)) hire people to test their products for them. Yes, they will sit you in a room, give you a program, and tell you to break it. And when you do, they will track what, when, why, and how it happened. Then they will come up with a fix for it. Honorbuddy doesn't have that kind of luxury. Given the scope of functions this bot performs, they need the communities help to find bugs and fix them. So if breaking things and reporting how isn't your cup of tea, don't use Honorbuddy until it comes out with a [Stable] tag.
The highest things on our priority list, are crashes, DCs, and stuff like that.
We do fix other bugs along the way (I usually fix a crash, then 3 bugs, a crash, 3 more bugs, etc)
We don't have a "hard-set" system of which bugs are dealt with first. Crashes and DCs are always the first to be fixed.
Since PVP 'works' (last I checked, it was running around fine, I may be wrong though), it's gone back down to the low end of the list.
If you have something specific to add, please, do so. Giving us general blanket statements like "PVP is broken, it doesn't move" doesn't help anybody, especially us.
@mezz0 & Vertraag; I agree, and don't agree at the same time. We shouldn't *have* to rely on users to file bug reports. But unfortunately, it's our only choice. We've made various avenues available to people to report their issues, etc. Most of the time; it's a user error, which is fine. We included a bug submitter in HB itself to alleviate some of the issues with submitting bugs. (Give us a description, how to reproduce it, and a short summary, the rest is handled for you)
Most of the time we receive "bug reports" with nothing but 1/2 a log, or snippets of a log with no information in it. (People automatically assume 1 error message is the cause of the trouble, when most of the time the error starts a few minutes ahead of that)
Lastly, I'm not sure what kind of psychics your company employs, but we're unaware of any way to find bugs we can't... find. We rely on users to report the bugs that we can't find, so we can fix them. We test as many things as we can before releasing, but it's not until it gets let loose into the wild, that things really start popping up.