January 2006 - otrs - OTRS mailing lists

Cannot send email through OTRSCannot send email through OTRS
by scott＠fingerworks.com 02 Jan '06

02 Jan '06

I am running otrs 1.3.2 on Debian. When I first set the system up emails sent out without a problem. At some point mails stopped sending (I'm not sure when although it may correspond with a server outage that we had). I never see any errors or bounced messages and the OTRS system log indicates that the mail was sent without error. Any ideas???? Thanks, Scott ------------------------------------------------- This mail sent through IMP: http://horde.org/imp/

1 0

SLA violation
by ali 02 Jan '06

02 Jan '06

hello everybody, is there any way to define for each customer an attrobutes that correspond to its contracted time-to-fix in the SLA. then once the ticket is clotured, we are able to know if the time-to-fix commitment has been fullfiled or not ? kind regards --------------------------------- Nouveau : téléphonez moins cher avec Yahoo! Messenger ! Découvez les tarifs exceptionnels pour appeler la France et l'international.Téléchargez la version beta.

1 0

Calendar problem
by David Kreuz 02 Jan '06

02 Jan '06

Hello, is there a way to configure Calendar for the Customer users to (only) show them the actions added by standard users? Do I have to set up AgentCalendar for Customers users? Thanks in advance, David Kreuz

1 0

AW: [otrs] OTSR Configuration Options
by shawn.beasley＠dlh.de 02 Jan '06

02 Jan '06

Dear Richard, First of all, your name was well selected. - The Great Petty!!! To the question about "We'd like our customers to be able to create their tickets using a web interface and to be able to self-select the appropriate queue. Is this possible?" This is of course possible over the customer.pl script. This only has to be available to customers. And you go to sysconfig: Config Options: Framework -> Frontend::Customer And set this option to yes CustomerGroupSupport: Then the queue that you want to have available to your customer have to be assigned to a group where the customer RW rights has. Vielen Dank, Shawn Beasley Support - IT -----Ursprüngliche Nachricht----- Von: otrs-bounces(a)otrs.org [mailto:otrs-bounces@otrs.org] Im Auftrag von Richard Petty Gesendet: Samstag, 31. Dezember 2005 01:16 An: otrs(a)otrs.org Betreff: [otrs] OTSR Configuration Options I'm evaluating OTSR to possible replacement of our current, in-house developed ticket system. I've printed and bounds the docs, studied them, and based on what I've read therein and in this mail list, I have some concerns about the way OTSR works versus how we'd like it to work. Our current ticket system does not maintain a user database; customer info like names, department numbers, and telephone numbers are properties of each trouble ticket. Several challenges arise from OTSR's management of users but, as sophisticated as OTSR appears, there may be ways to make it work for us. First, everyone can authenticate to a corporate read-only LDAP database. This works fine. But is there a way to configure OTSR to auto-register customers when they first authenticate, maybe loading the backend SQL user database with info pulled from the LDAP authentication database? We'd like our customers to be able to create their tickets using a web interface and to be able to self-select the appropriate queue. Is this possible? --Richard Austin, Texas _______________________________________________ OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs Support oder Consulting für Ihr OTRS System? => http://www.otrs.de/

1 0