Hi Steve,
if you don't have a requirement that you also want to restrict some
people to show only tickets for one site, you can get away with using
a separate customer_id per company.
If you DO have the requirement that some customers need to see only
the tickets of one site, while others need to
Hi Steve,
Did you try a search on the archive (like mail-archive.com/otrs@otrs.org)
for something like "multiple customer id"
Basically it is permitted but I've to refresh my mind too... ;)
HTH
MV
On Wed, May 19, 2010 at 9:16 PM, Steve Clark wrote:
> Hello all,
>
> I have installed OTRS 2.4.
Steve Clark wrote :
Am I posting to the wrong list? Is there a
noobie list I should be posing the following
questions to?
Hi Steve,
this is the right list, but so far nobody who has read your mail seems
to know the answer. I suggest to wait a week and then ask again or to
try http://forums.o
Hi,
Am I posting to the wrong list? Is there a
noobie list I should be posing the following
questions to?
Your indulgence is appreciated.
On 05/21/2010 07:15 AM, Steve Clark wrote:
On 05/19/2010 03:16 PM, Steve Clark wrote:
Hello all,
I have installed OTRS 2.4.7 and have it functioning, but
On 05/19/2010 03:16 PM, Steve Clark wrote:
Hello all,
I have installed OTRS 2.4.7 and have it functioning, but
am perplexed on how to configure it for our environment.
We have many customers that each have many sites.
Example:
Company A HQ.
Company A site 1.
Company A site 2.
Hello all,
I have installed OTRS 2.4.7 and have it functioning, but
am perplexed on how to configure it for our environment.
We have many customers that each have many sites.
Example:
Company A HQ.
Company A site 1.
Company A site 2.
Company A site 3.
...
Company A site 300.
W
