Hi,
Does anyone have a script for adding Customer users to groups?
We have a large number of customers and want to add sub-sets of these to a
number of groups.
I've tried modifying the script otrs.AddUser2Group.pl (which adds Agents to
groups) without success - probably not surprisingly since
and discussions about OTRS.
Subject: Re: [otrs] Command-line script for adding Customer users to groups?
It would be much simpler to perform this operation via SQL directly on OTRS's
database
On Fri, Sep 6, 2013 at 4:33 PM, Stanford, Philip N.
p...@noc.ac.ukmailto:p...@noc.ac.uk wrote:
Hi,
Does
...@gmail.commailto:bogdan.io...@gmail.com wrote:
It would be much simpler to perform this operation via SQL directly on OTRS's
database
On Fri, Sep 6, 2013 at 4:33 PM, Stanford, Philip N.
p...@noc.ac.ukmailto:p...@noc.ac.uk wrote:
Hi,
Does anyone have a script for adding Customer users to groups?
We have a large
The Netherlands
T: +31 71 8200 255
I: http://www.otrs.com
Happy Birthday OTRS ! - 10 years of Open Technology, Shared Innovation and
Advanced Customer Service - Let's move on together
On Fri, Sep 6, 2013 at 4:31 PM, Stanford, Philip N. p...@noc.ac.uk wrote:
Thanks Gerald
We do need ‘customer group
Hi, in the sections of the Dashboard view, it's possible to change the SortBy
attribute by using the Sysconfig Ticket - Frontend::Agent::Dashboard options
page for the relevant Dashboard section.
For example you can specify 'SortBy=Age' or 'SortBy=Priority'.
I am wondering if it's possible
Hi
I support a couple of OTRS systems (3.2 and 3.3) which have CustomerUser data
stored in the normal local database backend. These do however authenticate
customers against AD LDAP.
I also support another 3.3 system which was set up from the outset so that
customers authenticate against AD
Hi
I had a working OTRS 4 test system, minimally configured, built on Centos 6.7
The system included OTRS::ITSM and packages such as FAQ, Master-Slave etc.
I thought I would upgrade that to the released version of OTRS 5.
I followed the procedure in
ated environment?
Check also SELinux.
El 21/10/2015 10:45 a. m., "Stanford, Philip N."
<p...@noc.ac.uk<mailto:p...@noc.ac.uk>> escribió:
Hi
I had a working OTRS 4 test system, minimally configured, built on Centos 6.7
The system included OTRS::ITSM and packages such as FAQ, Mas
Hi - I am also seeing a very similar repeated message since upgrading a test
system from 4.x to 5.0.1:
OTRS-otrs.Daemon.pl - Daemon
Kernel::System::Daemon::DaemonModules::SchedulerTaskWorker-04:
[Error][Kernel::System::Daemon::DaemonModules::SchedulerTaskWorker::Cron::Run][Line:119]:
Hi
We've been discussing some changes in our help-desk workflow which we may want
to implement as part of a forthcoming move to OTRS 5, from 3.0
The normal OTRS behaviour for a ticket created from an incoming mail is for it
to remain 'new' and 'unlocked' until an agent replies to the customer.
10 matches
Mail list logo