Hi Jeroen,
On 23.06.2010, at 16:03, Jeroen van Meeuwen (Kolab Systems) wrote:
In the use case you described now, where a partner needs access to all
tickets of customers of that partner, I guess OTRS could need some
improvement indeed. Right now the process would be that you create a
field
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
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
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
Hi there,
My name is Jeroen van Meeuwen, and I'm relatively new to OTRS.
I wanted to acquire some feedback on the following scenario, since I didn't
seem to able to simply deploy it using current OTRS functionality.
Kolab Systems AG is the vendor for Kolab Groupware solutions, and as such
