Hi Vadim, I cannot confirm this. TicketSearch() correctly processes CustomerID, I even added a unit test to verify this - if an invalid CustomerID is sent, the ticket is not found. You can see this if you print the generated SQL string. Regards, mg Am 26.11.12 17:20, schrieb Vadim S. Goncharov:
Hi,
I've found that Kernel/Modules/CustomerTicketOverview.pm still calls:
CompanyTickets => { All => { Name => 'All', Prio => 1000, Search => { CustomerID => [ $Self->{CustomerUserObject}->CustomerIDs( User => $Self->{UserLogin} ) ], OrderBy => $Self->{OrderBy}, SortBy => $Self->{SortBy}, CustomerUserID => $Self->{UserID},
but TicketSearch() routine has stopped to process 'CustomerID' in rev. 1.197, it is completely ignored for years ago.
What I was actually trying to do when found this - I was trying to make work "My Company Tickets" feature. The intuitive way of setting "company" field to group borrowed from LDAP group:
[ 'UserCustomerID', 'CustomerID', 'mail', 1, 1, 'var', '', 0 ], [ 'UserCustomerIDs', 'CustomerIDs', 'ou', 1, 1, 'var', '', 0 ],
didn't work...
-- Martin Gruner Senior Developer R&D OTRS AG Europaring 4 94315 Straubing T: +49 (0)6172 681988 0 F: +49 (0)9421 56818 18 I: www.otrs.com/ Geschäftssitz: Bad Homburg, Amtsgericht: Bad Homburg, HRB 10751, USt-Nr.: DE256610065 Aufsichtsratsvorsitzender: Burchard Steinbild, Vorstand: André Mindermann (Vorsitzender), Christopher Kuhn, Sabine Riedel It's raining... OTRS Feature Add-Ons! Bis zu 10 kostenlose OTRS Feature Add-Ons und professionellen Hersteller-Support – Werden Sie jetzt Service-Subscription-Kunde!