Am I the only one with this kind of problem?
2013/5/31 Finetti, Stefano
> Greetings to all.
>
> Since the upgrade to 3.2.7, I've noticed that customer search in Customer
> Information Center (The AJAX modal window), has become case sensitive on
> the first row (CustomerID/Customer Company Name)
Two customers, customer a and b, belong to the same company. It
appears that customer b could reply to customer a's ticket. How can't
I restrict customer b's access to customer a's tickets to read only?
Also, is there block a customer from changing ticket state (ie.. open,
closed successful, clo
Oh, thank you very much!
It works!
2013/6/6 Gerald Young
> You will need to add an index (number) to the keys for the additional
> backend.
>
> $Self->{'Customer::AuthModule'}
> $Self->{'Customer::AuthModule1'}
> ...
> $Self->{'Customer::AuthModule::DB::Table'}
> $Self->{'Customer::AuthModule:
You just needs to set a different default state for new phone tickets other
than New (open, asigned, etc)
That should do what you need.
Regards
2013/6/6 Simon Allison
> ** **
>
> Hi
>
> ** **
>
> I setup a notification to send an email, whenever there was a new ticket
> into a queue, but
OK, it's pretty clear that I did something wrong in setting up the
externalDB. I pretty much pasted the example from the admin guide into
Config.pm and edited it. It's at least partially working because I can
see the customers and create tickets for them. In addition to the weird
thing tha
When I create a new ticket in OTRS (Tickets -> New Phone Ticket) the
form seems to have two different places to select a customer.
One is an edit box labeled "From Customer:" where I can start typing a
customer's name or email address and it starts showing me options I can
pick from.
The other
Or, alternatively, don't let them get notifications of tickets in the
default queue. Just let them get "you've been assigned owner" notifications.
On Fri, Jun 7, 2013 at 11:11 AM, Gerald Young wrote:
> >But the system doesn’t create the tickets in different queues, creates
> in the same queue
>But the system doesn’t create the tickets in different queues, creates in
the same queue.
The system doesn't create tickets. And, how does this statement apply to
your original question?
On Fri, Jun 7, 2013 at 8:59 AM, Simon Allison wrote:
> But the system doesn’t create the tickets in differe
It should be possible, check this section of the documentation:
http://doc.otrs.org/3.2/en/html/external-backends.html#configuration-customer-auth-backend-db
You should set $Self->{'Customer::AuthModule::DB::CryptType''} to
'plain' in order to authenticate against the unencrypted passwords.
I *n
But the system doesn't create the tickets in different queues, creates in the
same queue.
From: otrs-boun...@otrs.org [mailto:otrs-boun...@otrs.org] On Behalf Of Gerald
Young
Sent: 06 June 2013 17:00
To: User questions and discussions about OTRS.
Subject: Re: [otrs] change owner of ticket, don
Hi Marc,
better late then never.
Great Hint with the ACLs, works like a charm.
Here's what I did for anyone searching for something similar, it's pretty much
the example from the documentation on disabling Ticket Close on the Raw Queue:
$Self->{TicketAcl}->{'ACL-Disable-IncidentReport-Tick
Hi Adam,
On Thu, Jun 6, 2013 at 7:27 PM, Adam Moffett wrote:
> I have an existing billing system where the user's passwords happen to be
> stored in MSSQL in plain text. This is an existing system written by
> another company and I am not at liberty to change it. Is there any way to
> configure
12 matches
Mail list logo
