Wes Plate wrote:
On 9/10/04 12:24 AM, Robert L Mathews wrote:
Sorry for the delay in submitting it; perhaps it's trivial enough (and
fixes a large enough bug) that it can make it into OTRS 1.3.
Please! :-)
I just looked into CVS and it seems like the fix didn't make it into
1.3.1. Any
OTRS main list wrote:
In the documentation on using LDAP to authenticate, to restrict
access to a list of people it is recommended that a posixGroup be
created. I know how to create a regular group in the Active
Directory, but how do I make a posixGroup? Is there some special
tool that comes
On 9/23/04 3:43 AM, Frederik Seiffert wrote:
I just looked into CVS and it seems like the fix didn't make it into
1.3.1. Any predictions about when it will be included? We'd rather like
to have an official release instead of a patched version.
Dang. I too was hoping the next upgrade was
I am trying to understand the QueueView so I can understand how many open tickets
there are, and who is working on them (owner). Why does the queueview only show
available tickets versus open (not yet closed) tickets, and what criteria is used
to determine if a ticket is available?
What is the
[EMAIL PROTECTED] wrote:
I am trying to understand the QueueView so I can understand how many
open tickets there are, and who is working on them (owner). Why does
the queueview only show available tickets versus open (not yet
closed) tickets, and what criteria is used to determine if a ticket
Thanks very much for that info. Can I get a definition of available tickets?
What makes a ticket available?
What criteria define if a ticket is shown on the queueview page?
MMP
___
OTRS mailing list: otrs - Webpage: http://otrs.org/
Archive:
On Thu, 23 Sep 2004 14:52:43 -0400, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Thanks very much for that info. Can I get a definition of available tickets?
The ticket has state new and has not been locked or responded to in any way.
The ticket has state open and has been unlocked by a user or
Hallo,
bestimmt bloss ne Kleinigkeit, aber ich finde die Lösung nicht.
Wenn Kunden Tickets via Mail einstellen bekommen wir bei Antwort
erstellen (E-Mail): die korrekte Anrede und Sig usw. (wurde von uns so
hinterlegt bei Empfangsbestätigung OTRS_CUSTOMER_SUBJECT[20])
Stellt der Kunde das
Hallo!
Ich habe am Afnag der Woche OTRS auf einem Testrechner installiert.
Es ist ein Debian/Woody mit einigen Backports.
Beim Versuch Mails abzurufen bekomme ich immer die Fehlermeldung:
merkur:/usr/local/otrs/bin$ ./PostMasterPOP3.pl
Use of uninitialized value in numeric eq (==) at
Die Einstellung, die Du suchst (Config.pm):
$Self-{FQDN} = 'yourhost.example.com';
und ggf. (falls explizit andere notification-addresse gesucht):
$Self-{NotificationSenderEmail} = 'otrs@OTRS_CONFIG_FQDN';
... und folgendes brauchte ich auch noch:
# ScriptAlias
# Prefix to
Nora Bernhard schrieb:
Hi :)
Ich finde keine Moeglichkeit, die Erinnerungszeit zu konfigurieren!?
Wenn ich ein Ticket auf 'pending' stelle, laeuft irgendwann die
Erinnerungszeit ab, aber das Email kommt erst viel spaeter (im Test: 1h
15min) - kann ich das irgendwo runtersetzen, dass in dem Moment
11 matches
Mail list logo
