Oorgo

Yeah, that was always a problem with some of the places where I worked. Bug tracking software is perhaps a Godsend for the software developers, but customers tend to find them chock full of jibberish they don't want to know about.

What you really need is bug tracking software that keeps the customers away from the technical details, but still acknowledges that they've filed a complaint.

The other problem is consolidating similar bugs into a main trunk. Sometimes fixing one bug could cascade-fix other bugs, but they still all have to be tested nevertheless.

It's a real pain in the ass. That's why they should be using UML. Supposedly. At least, that's what they claim here in school. I hate UML, but I understand its need. sigh

So your suggestion is.... :P

Yeah, it's a pain, the good part about this situation is it's not going to be accessible to the customers, just internally, and to customer service (and only what they need to see).

I actually used UML on the most recent thing I was working on. I liked it a lot. I liked auto-generating code from UML diagrams.

And by the time I really got into things, I might as well have thrown the whole thing out. Not that it was a total waste of time. It did help me get my head around a few things, but I'm not convinced I couldn't have done as much with a pad and paper. Maybe saved myself a bit of typing.

You know that Patton quote about plans until you meet the enemy? I think that's what UML is. It makes all the promises that people like to hear, reducing coding to a few diagrams suitable for power point presentations.

Don't know....might use it again. It's pretty and all that.

Anyway, on topic, I can't give you any hints, I'm looking for the same thing. Except that it sounds like you're looking for help desk or ticketing software more than bugtracking. There's a million and half of those, too, and the only bookmark I had isn't going anywhere right now.

So, that's totally useless. HTH.