Re: [dev] OTRS for Customer Companies using LDAP

2010-06-23 Thread Jeroen van Meeuwen (Kolab Systems)
Michiel Beijen wrote: Hallo Jeroen, We applaud that your company is willing to contribute to OTRS. Cheers! o/ o/ o/ \o \o \o But first I'd like to point out that I guess your patch is not needed to realize the scenario you want. The Customer ID is not necessarily unique per customer

Re: [dev] OTRS for Customer Companies using LDAP

2010-06-23 Thread Michiel Beijen
On wo, 2010-06-23 at 13:47 +0200, Jeroen van Meeuwen (Kolab Systems) wrote: My question is, however, where the Customer ID accounting goes. Given that the customer users come from LDAP, I'm assuming their Customer ID must also come from LDAP? One possible future scenario in the Kolab

Re: [dev] OTRS for Customer Companies using LDAP

2010-06-23 Thread Jeroen van Meeuwen (Kolab Systems)
Michiel Beijen wrote: On wo, 2010-06-23 at 13:47 +0200, Jeroen van Meeuwen (Kolab Systems) wrote: One possible future scenario in the Kolab Systems case could be that we provide the infrastructure for partner @partner.com to support customer @customer.com. I would add the

[dev] [PATCH] Enable configuration for locking in AgentTicketBulk

2010-06-23 Thread Jeroen van Meeuwen (Kolab Systems)
Hi there, Attached is a patch to enable a 'RequiredLock' setting for Frontend::Module::AgentTicketBulk, much like other frontend modules have a similar setting, based on rel-2_4. Kind regards, -- Jeroen van Meeuwen Senior Engineer, Kolab Systems AG e: vanmeeu...@kolabsys.com t: +316 42 801