Hi Volker,
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?
mmh, I agree it wouldn't be that simple and it could cause unwanted chain reactions. I also agree that otrs' purpose is also to globally keep a history. So it can be a bad idea. But I can imagine me wanting to delete a queue and all it's content, why not. A test queue, an old queue from an old customer that I don't want to see anywhere anymore. This wouldn't imply automatic deletion of related users, customers, supporters. If we'd like to delete a Customer, we could have the choice either to delete all related tickets or having them reassigned. If we'd like to delete an user/supporter, related tickets could receive "unknown" in these fields, or ownership back to the administrator (up to him to sort all out then), or an option to reassign all to somebody else of our choice. Note that I'm only brainstorming... I know that everybody has different needs and there wouldn't be a single and easy solution. But we can have different sets of options depending on what we'd like to delete. And we could even have an option for removing the 'delete' option, for sysadmins who don't want it!...
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....
That's why I'd prefer to do it under otrs' control!
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.
Well it's quite possible, it's just that I for one wouldn't like to amass tons of "disabled crap" in the users' workspace. Or at least I wouldn't like to see it, and then put it under the carpet with a "hidden" parameter as Trevor is working on... regards, Eric