On 4/27/05, Cainkar, Paul
Carlos,
Q#1:
SuSE 9.1 Good choice :). It also works on 9.2 with a little modification.
Well, first of all I´m impress on the quick answer, so thanks =)
Q#2:
You can't delete users, but you can disable their access, effectively deleting them. Since OTRS is a database, if you wanted to delete a user you would have to delete all their respective tickets, otherwise you would lose the referential integrity of the platform as a whole. The last thing you want in a database is orphaned tickets. Instead of making provisions for the mass deletion of a user's tickets (who would want this anyways? You'd loose historical data.), they've made a way to disable that user's account. The user will still be listed, but from the users standpoint, he no longer exists. An override for test users or ability to hide users would be nice, but that's another story.
So basically one has to really have the design of the whole system before starting to define clients, customers, etc? What did you do when you started using OTRS?
Q#3:
I wouldn't mess in the database yourself, unless you have a good knowledge of databases and the complex schema schema which OTRS uses. In any case, BACKUP FIRST! You might be better off reinstalling. On suse 9.1, you can turn a fresh system into a functional installation in around 10 minutes flat if you use the RPM. Just be sure to move your config file over if you use anything special (IE: LDAP/Active Directory.).
Ok, so handling mysql is out of the question, hope to finish the pdf tonight so I can read it over again tomorrow :) Bye.