Obviusly, it's not a great idea, but if you ensure that user, queues, ... hasn´t got any ticket associated, not trouble may causes that you erase an user. When I ended the test time I closed all tickets as "root", moving all tickets before to an admin queue that I not remove.
im not that shure that the ability to delete things would be a great idea.
or even an essential option...
what should happen with the tickets in that queue? or the tickets refering
tickets in that queue? or users that had tickets in that queue. or.or.or.
there would be a lot of unresolved references in every case. how to handle
them? Delete them all?
you are free to delete things in the db. with the tools of the db. and you
are free to live with a corrupted system then....
so in the view of system integrity i am pretty sure that the next version
of otrs wont have the ability to delete things, but it will still have the
ability to disable things.
just 2ct..
Li
_______________________________________________
OTRS mailing list: otrs - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/otrs
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
Support oder Consulting für Ihr OTRS System?
=> http://www.otrs.de/
--
Alvaro López
alopez@genetsis.com
www.genetsis.comC/ Francisca Delgado, 11, 3º.
Arroyo de la Vega, 28108 - Alcobendas - (Madrid)
T. 916574120 - F. 916574130La información contenida en el presente correo electrónico es secreta y confidencial, y es de uso exclusivo del destinatario arriba indicado. Si usted no es el destinatario señalado, por favor, notifíquelo al remitente y borre este mensaje de su disco duro. Cualquier otro uso que haga del mismo está estrictamente prohibido.
_______________________________________________
OTRS mailing list: otrs - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/otrs
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
Support oder Consulting für Ihr OTRS System?
=> http://www.otrs.de/