
Hi Gerald, Thank you so much for that clarification. It made things click for me. Lars From: otrs-bounces@otrs.org [mailto:otrs-bounces@otrs.org] On Behalf Of Gerald Young Sent: Wednesday, December 08, 2010 9:01 PM To: User questions and discussions about OTRS. Subject: Re: [otrs] Problem CustomID(s) and "My tickets" and "Company No, CustomerID changes should not affect "My Tickets". "My Tickets" is based upon the customer as an individual. "Company Tickets" is based upon tickets which have a CustomerID that is the same as that which is assigned to the customer user. It's (IMO) an unfortunate naming scheme. For simplicity, let's just say that the username (login) is what determines what's in the customer's "My Tickets". The CustomerID is what determines what's in the customer's "Company Tickets" Users who have the same CustomerID will see the same tickets in "Company Tickets" ... if the ticket was created when the CustomerID is the same. That means that if a ticket was created when the customer user's customerID was the user's email address, until/unless that is changed (by Generic Agent or re-assigning the customer to the ticket), the ticket has a CustomerID of the email address. (CustomerID is stored in the ticket). So what's CustomerIDs about? In the standard AD configuration, individual users have unique CustomerID (email address), because isolation of the ticket information is more secure than what you're trying to accomplish (at least, by default). Because of individual CustomerID per user, a manager will need to have more than one CustomerID to see all the individual customers in "Company Tickets". To offset that, "CustomerIDs" was implemented to allow a user (manager-type) to have a list of CustomerID so he can see the tickets from departments (or lists of individual email addresses) in *his* "Company Tickets". To allow everyone to see everyone else's tickets, this makes a big matrix mess (because everyone will have to have everyone else's CustomerID in her own CustomerIDs list) unless everyone has the same CustomerID. Hope this wasn't too confusing. If it was, consider Customer user to be an individual, and CustomerID to be a group name. Members of the same CustomerID can see the tickets attached to the same CustomerID in "Company Tickets".