This is a notification from the Help Desk.
On Jul 02, 2011 @ 03:50 pm, itlj@gyldendal.dk wrote:
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".
==Ticket History==
On Jul 02, 2011 @ 03:48 pm, crythias@gmail.com wrote:
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".
------
On Jul 02, 2011 @ 03:48 pm, erik.van.ast@suzohapp.nl wrote:
Hi Gerald,
Thank you for your reply.
When I do this, the customers won't have any "My tickets" as they all
have the same CustomerID I presume? Or am I wrong?
Kind regards,
Erik
-----Original Message-----
From: otrs-bounces@otrs.org [mailto:otrs-bounces@otrs.org] On Behalf Of
otrs-request@otrs.org
Sent: woensdag 8 december 2010 19:04
To: otrs@otrs.org
Subject: otrs Digest, Vol 27, Issue 24
Send otrs mailing list submissions to
otrs@otrs.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.otrs.org/cgi-bin/listinfo/otrs
or, via email, send a message with subject or body 'help' to
otrs-request@otrs.org
You can reach the person managing the list at
otrs-owner@otrs.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of otrs digest..."
Today's Topics:
1. No notification for agents and customers after new ticket
and new tickets created by email are not created (Erik van Ast)
2. Re: Problem CustomID(s) and "My tickets" and "Company
tickets" (Gerald Young)
3. Re: Antw: Re: Antw: Upgrading from 2.4.9 to 3.0.3: pain
(Martin Gruner)
4. Re: Next ticket state (Dominique 'NetAndroid' Schramm)
5. Bug Tracking - or other bug tracking integration (Clayton Doty)
----------------------------------------------------------------------
Message: 1
Date: Wed, 8 Dec 2010 13:45:51 +0100
From: "Erik van Ast"