Gratz for a great product

[triplef]

After searching and trying over 10 different systems in the past 2 years., combining multiple company products to achieve what this is doing.. this is simply the best one so far..

As seen in these forums , some people think they own kayako's dev team by asking , no " ORDERING" kayako to do this or that..

A product of this magnitude is really complicated to manage and even to upgrade or fix bugs.. please let the bugs be bugs, and if you can't wait for revisions , then hire a private coder to update your code.


The product has a few quirks.. ( example : login livesupport when staff memeber has no assigned depts yet.) will crash.. BUT any one with an iq over 4 can fix this in no time..


What i would suggest is making the bugs list a oder by date desc and going from there till the bug is resolved.. this way bugs would be dealt in orde r received.. there will always be bugs as new features are added and this is the only way to go..


PERFECT product.. got last 4 hours ago and installed, configgured, and runnign live right now for 4 depts.

Keep it up , may the RAID be with you ( for bug hunting ) and peace !

from the whole Voicemeup Team

[Sheep]

Originally Posted by triplef

What i would suggest is making the bugs list a oder by date desc and going from there till the bug is resolved.. this way bugs would be dealt in orde r received.. there will always be bugs as new features are added and this is the only way to go..

This?
http://bugs.kayako.com/index.php

[craigbrass]

Yes, as Antoine pointed out, the bugs section does not get bugs closed until one of the developers has fixed them. End users and admins can order them by clicking the column titles.

[Jamie Edwards]

Triplef,

Great to hear you are pleased with the product, thanks for posting your comments

[triplef]

i meant.. not goign over a bug to do it later ( ill do it when im on the tickets modules bugs example) ..so it has to be dealt with ...

i guess thats more management issues then anything else..

Get the whip out , and walk down the roach cruncher isle lol

[craigbrass]

So you mean like as soon as a bug is looked over, fix it?

The way it works at the moment is :-
1. It gets submitted.
2. Somebody confirms the existance of the bug in an unmodified version. The person who usually does this is Jamie as he is Operations Manager.
3. The bug gets passed across to a developer if it is confirmed in the previous step. The developers work through the bugs in date order fixing them as they view them.

So, as soon as developers see bugs and they are able to sort them, they do.

[Jamie Edwards]

And there is a 4th step to that - the bug fix is tested by a Manager and the Testers team.

[craigbrass]

Ah, cool. The current system works fine I think.