At 22:12 14.09.2005, you wrote:

...

Hi all,

I can't figure out how to remove a queue, or an e-mail address... or a lot of other options in the Admin area.

In the left part I can select current items to EDIT, and in the right part I can ADD NEW items. But there seems to be no option to REMOVE items. Should I slap myself for not looking at the right place, or is it really true OTRS lacks this option?

Ability to delete things would indeed be an essential option. As a new otrs user, I'm somewhat surprized it doesn't exist. Maybe in next release...

Eric

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

I believe that it truly would be a 'good thing' to be able to delete Queues, e-mails etc. One possibility would be to create an 'Orphan' queue that objects get assigned to that end up without an owner. Another option would be to warn the user that an object has items depending on it and to give them a list of options. Alternately, a preference could be to not display entries that have been disabled! I'm working on adding this functionality to the system but I've been swamped with work recently :-/. Trevor On 9/15/05, Alvaro Lopez wrote:

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.com http://www.genetsis.com C/ Francisca Delgado, 11, 3º. Arroyo de la Vega, 28108 - Alcobendas - (Madrid) T. 916574120 - F. 916574130 La 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/

-- Heredocs, theredocs, everwhereadocsdocs old macdonald had a server farm he eyed the I/O