Hi, Mark Mertel a écrit:

Kannan, it is unfortunate there is no UI for deleting users, nor is there a method in Kernel::System::User to accomplish this. There may be some referential integrity constraints in the database which may make it a bad idea to delete users - i.e. fields in other table which rely on a corresponding record in the user table in order to join properly. I am not familiar enough with OTRS to answer that question. However, the SQL to add a user is easily found in the Kernel::System::User->UserAdd method, and one can easily extrapolate the corresponding delete statement accordingly. The same is true for Queue and SystemAddress. You may be able to formulate the appropriate SQL, but executing it may be a problem if there is other data which depends on it. Better check with the OTRS folks on this first. my $deleteSQL = "DELETE system_user where login = 'login_name'";

In order not to mess up your DB, use the "valide" field both in users and customer users ... (it's quite in every object props !) or if you just want to delete some samples you entered to "play" with Otrs, just create a fresh new DB ... but be very careful modifying your DB manually, you may have strange things later ... MaNU

...

Dear All,

I have installed OTRS and slowly getting acquainted with its nice features. Want to know whether there is a provision for deleting users, ( both customer and Agent ) , Queue and System Address. If there is no interface , kindly guide me about the sql's to run on the DB for the removal of the above that will also delete all the dependencies.

Also it will be very helpful if some one can tell me about how to restrict the queues ( OR emai id's ) that gets listed in the To field of the Customer Message interface that is used to create New Ticket. ( That is , I don't want to display all the queues OR system emai ids in the New Ticket Creation Page because this causes confusion in the customer users ).

Again, congrats to the developers of OTRS for a really good product .

Thanking you,

Kannan.

Yahoo! India Matrimony: Find your partner online.Post your profile.

--- Mark Mertel mmertel@olympus.net Phone 206-322-9074 Cell 206-409-2018 _______________________________________________ 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/

On Friday, December 26, 2003 3:34 AM Mark Mertel wrote:

It would probably be a good idea for the long term to provide a delete method in the object model for each object which can be saved to the database. Within these methods could be handled any type of action regarding cascading deletes, or updating any reference tables with some default value, i.e. if you wished to delete a user you would probably want to update any trouble tickets created by that user toi some system user account.

A feature like the above is most likely to be built in the near future. Feel free to contribute ideas and/or concrete patches/code on the developers' list dev@otrs.org. Robert Kehl -- ((otrs.de)) :: OTRS GmbH :: Norsk-Data-Str. 1 :: 61352 Bad Homburg http://www.otrs.de/ :: Tel. +49 (0)6172 4832388

Hi i have change today my Mail server and now i have : [root@www-appli bin]# ./PostMasterPOP3.pl Message 1/1 (support@phibee.net@pop.phibee.net) ERROR: OTRS-PM3-10 Perl: 5.8.1 OS: linux Time: Thu Jan 15 15:55:56 2004 Message: No StateID for new found! Traceback (6616): Module: Kernel::System::Ticket::State::StateLookup (v1.14) Line: 74 Module: Kernel::System::Ticket::CreateTicketDB (v1.55) Line: 185 Module: Kernel::System::PostMaster::NewTicket::Run (v1.38.2.1) Line: 84 Module: Kernel::System::PostMaster::Run (v1.31.2.3) Line: 209 Module: main::FetchMail (v1.9.2.2) Line: 169 Module: ./PostMasterPOP3.pl (v1.9.2.2) Line: 106 ERROR: OTRS-PM3-10 Perl: 5.8.1 OS: linux Time: Thu Jan 15 15:55:56 2004 Message: No StateID!!! Traceback (6616): Module: Kernel::System::Ticket::CreateTicketDB (v1.55) Line: 189 Module: Kernel::System::PostMaster::NewTicket::Run (v1.38.2.1) Line: 84 Module: Kernel::System::PostMaster::Run (v1.31.2.3) Line: 209 Module: main::FetchMail (v1.9.2.2) Line: 169 Module: ./PostMasterPOP3.pl (v1.9.2.2) Line: 106 ERROR: OTRS-PM3-10 Perl: 5.8.1 OS: linux Time: Thu Jan 15 15:55:56 2004 Message: Need TicketID! Traceback (6616): Module: Kernel::System::Ticket::Article::CreateArticle (v1.27.2.3) Line: 47 Module: Kernel::System::PostMaster::NewTicket::Run (v1.38.2.1) Line: 107 Module: Kernel::System::PostMaster::Run (v1.31.2.3) Line: 209 Module: main::FetchMail (v1.9.2.2) Line: 169 Module: ./PostMasterPOP3.pl (v1.9.2.2) Line: 106 ERROR: OTRS-PM3-10 Perl: 5.8.1 OS: linux Time: Thu Jan 15 15:55:56 2004 Message: Need TicketID! Traceback (6616): Module: Kernel::System::Ticket::SetCustomerData (v1.55) Line: 524 Module: Kernel::System::PostMaster::NewTicket::Run (v1.38.2.1) Line: 197 Module: Kernel::System::PostMaster::Run (v1.31.2.3) Line: 209 Module: main::FetchMail (v1.9.2.2) Line: 169 Module: ./PostMasterPOP3.pl (v1.9.2.2) Line: 106 ERROR: OTRS-PM3-10 Perl: 5.8.1 OS: linux Time: Thu Jan 15 15:55:56 2004 Message: Need TicketID! Traceback (6616): Module: Kernel::System::Ticket::State::SetState (v1.14) Line: 131 Module: Kernel::System::PostMaster::NewTicket::Run (v1.38.2.1) Line: 232 Module: Kernel::System::PostMaster::Run (v1.31.2.3) Line: 209 Module: main::FetchMail (v1.9.2.2) Line: 169 Module: ./PostMasterPOP3.pl (v1.9.2.2) Line: 106 ERROR: OTRS-PM3-10 Perl: 5.8.1 OS: linux Time: Thu Jan 15 15:55:56 2004 Message: Can't process email with MessageID <<00ce01c3db77$d80bd0b0$6432a8c0@Jerome>>! Please create a bug report with this email (var/spool/) on http://bugs.otrs.org/! Traceback (6616): Module: Kernel::System::PostMaster::NewTicket::Run (v1.38.2.1) Line: 237 Module: Kernel::System::PostMaster::Run (v1.31.2.3) Line: 209 Module: main::FetchMail (v1.9.2.2) Line: 169 Module: ./PostMasterPOP3.pl (v1.9.2.2) Line: 106 Connection to pop.phibee.net closed. The Otrs module are not on the same server of the mail server ! what is the module with the problemes ? thanks for your help

Kannan, there's always a way - and if not, there's probably a hack. What criteria are you planning on using to filter the queues ? I mean, why display some and not others, and if they don't display, why even have them ? You could probably us the 'valid' strategy here as well, couldn't you ? On Fri, 2003-12-26 at 02:59, kannan v wrote:

Hi, Thanks all. It will be very helpful if there is a provisioin for deleting the obects from the database in an enterprise scenario with a large no of users.. For now , i will use the "valid" field to serve my purpose.

Can any one answer my second problem . ( Listed Below )

...

Also it will be very helpful if some one can tell me about how to restrict the queues ( OR emai id's ) that gets listed in the To field of >the Customer Message interface that is used to create New Ticket. ( That is , I don't want to display all the queues OR system emai ids in the New Ticket Creation Page because this causes confusion in the customer users ).

Thankin you,

Kannan.

Mark Mertel wrote: After getting OTRS installed on my laptop, I see that all should need to do is mark the user, queue, whatever to invalid, or invalid-temporarily. So, don't go mucking around with your database ;>)

kannan v writes:

> Dear All, > > I have installed OTRS and slowly getting acquainted with its nice features. Want to know whether there is a provision for deleting users, > ( both customer and Agent ) , Queue and System Address. If there > is no interface , kindly guide me about the sql's to run on the DB for the > removal of the above that will also delete all the dependencies. > > Also it will be very helpful if some one can tell me about how > to restrict the queues ( OR emai id's ) that gets listed in the To field of the Customer Message interface that is used to create New Ticket. > ( That is , I don't want to display all the queues OR system emai ids > in the New Ticket Creation Page because this causes confusion in the > customer users ). > > Again, congrats to the developers of OTRS for a really good product . > > Thanking you, > > Kannan. > > > > > > > > > Yahoo! India Matrimony: Find your partner online.Post your profile.

--- Mark Mertel mmertel@olympus.net Phone 206-322-9074 Cell 206-409-2018

_______________________________________________ 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/ Yahoo! India Matrimony: Find your partner online. Post your profile.

______________________________________________________________________

_______________________________________________ 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/