The best way to accomplish this, and correct me if I am wrong, is with roles.
Roles allow for OTRS to grant access based upon the roll. For example, you
could have the role of supervisor where they can see the the tickets for all of
the user (customer or agent) that they supervise.
Below is
Thanks Jeremy
Unfortunately roles only cover the rights for the Agent user, not for the
Customer user.
Perhaps I should have been more clear - we need our Customer users (on the
customer.pl frontend) to be able to see each others tickets.
2009/3/30 Jeremy Adams
> The best way to accomplish thi
Tickets or other method of viewing
anothercustomer's tickets
Thanks Jeremy
Unfortunately roles only cover the rights for the Agent user, not for the
Customer user.
Perhaps I should have been more clear - we need our Customer users (on the
customer.pl frontend) to be able to see each others ti
Maurício
Thanks, that explains that CustomerIDs does work how I thought it did. It's
no good - we have far too many customers to do this with. With only a dozen
or so I can understand this being an effective solution, but it's
unmanageable and unwieldy for the amount we need to be dealing with.
2
Further to this, I've come up with the following map which solves the
problem:
Map => [
# note: Login, Email and CustomerID needed!
# var, frontend, storage, shown, required,
storage-type
[ 'UserSalutation', 'Title', '
