October 2009 - otrs - OTRS mailing lists

OTRS + CRM Implementation
by Chris Watt 26 May '25

26 May '25

I have been googling this for hours and it seems to have been mentioned on here but no one has ever given anything. What I want to do is link OTRS with a CRM program like SugarCRM (or similar). Has anyone done this before/know how to do it? Basically I want the tickets to be copied into SugarCRM automatically, with all approriate fields, and customers to be stored in the same location. I read somewhere that one guy had done it but he provided no further info. Cany anyone help? Cheers ~Chris

3 2

Thorsten Kocher/Spirit21 ist außer Haus.
by TKocher＠spirit21.de 19 Apr '17

19 Apr '17

Ich werde ab 13.05.2005 nicht im Büro sein. Ich kehre zurück am 30.05.2005. Vielen Dank für Ihre Email. Leider befinde ich mich bis Montag, 30. Mai 2005 außer Haus und kann daher Ihre Nachricht nicht bearbeiten. Bitte rufen Sie mich in dringenden Fällen mobil unter 0172 6377392 an. Vielen Dank für Ihr Verständnis. Thorsten Kocher Ich werde Ihre Nachricht nach meiner Rückkehr beantworten.

36 63

Custom TicketMenu Module for custom link in ticket zoom
by Alessio Tosi 26 Aug '10

26 Aug '10

I'm trying to create a custome Ticket Menu module that open another web application passing ticket information: TicketID and Ticket Number I've created a new module in /Output/HML TicketModuleChiamate.pm as mentioned in http://doc.otrs.org/developer/2.2/en/html/x533.html#ticket-module-menu with declaration of the package package Kernel::Output::HTML::TicketMenuChiamate; and registered the module in Config.pm # for ticket recording menu $Self->{'Ticket::Frontend::MenuModule'}->{'900-Chiamate'} = { 'Action' => 'AgentTicketChiamate', 'Module' => 'Kernel::Output::HTML::TicketMenuChiamate', 'Name' => 'Chiamate' }; What I'd like to do is open a new web page with an url I've changed the code to do $Self->{LayoutObject}->Block( Name => 'MenuItem', Data => { %{$Param{Config}}, %Param, Name => 'Chiamate', Description => 'Apri una chiamata Supporto!', Link => 'http://chiamate.osi.lan/default.aspx?&TicketID=$QData{"TicketID"}&TicketN umber=$QData{"TicketNumber"}', }, ); but when I click on the link I'm redirected to http://otrsDNSname/otrs/index.pl?http://chiamate.osi.lan/default.aspx?&Tic ketID=545803&TicketNumber=2063589 Is it possible to ignore the base url that is put at the beginning of the url Ciao AleX

2 1

Customer Map
by Mikola Rose 24 Aug '10

24 Aug '10

On the new features video, there is a dashboard item called customer map. Is this a module that needs to be installed? Mik Rose

5 8

Adding CustomerID column to 2.4 dashboard lists
by John Murray 08 Feb '10

08 Feb '10

The new dashboard feature of 2.4 is very cool, but we wanted to see customer information about listed tickets. Here's how I added a column to do this. Amended Kernel/Output/HTML/Standard/AgentDashboardTicketGeneric.dtl as follows: In dtl:block:ContentLargeTicketGenericRow section, add the following before the "Time" TD element: <td width="10%"> <a href="$Env{"Baselink"}Action=AgentTicketCustomer&TicketID=$QData{"TicketID"} " onmouseover="window.status='$JSText{"Customer history"}'; return true;" onmouseout="window.status='';"> <div title="$QData{"CustomerUserID"}">$QData{"CustomerID","15"}</div> </a> </td> A few lines later in the dtl:block:ContentLargeTicketGenericNone block increase the colspan from 3 to 4. I hope this is useful to others. John Murray George James Software 42-44 High Street Shepperton TW17 9AU United Kingdom Registered in England number 2568792 +44-1932-252568 www.georgejames.com

10 13

Circumvent the FAQ Article's subject to be appended to the response-email's subject
by Stefan Guha 05 Jan '10

05 Jan '10

Hi! We are using the FAQ module and agents of our OTRS helpdesk use the texts in the FAQ collection in responses to customers. Each time this is done then the subject of the Email is appended by the Title of the FAQ article. Example: 1. Open "Compose answer (email)" Subject will read like Re: [Ticket#1012345] Test Message to Support 2. Click the FAQ button. Popup opens. 3. Select appropriate FAQ article. Say, it's called "Easy Problem, Easy Solution" Hit the button "Done" which will insert the article's text in to the email. 4. The subject of the message will be changed to Re: [Ticket#1012345] Test Message to Support - Easy Problem, Easy Solution Some time now I have spent on looking in the configuration for some switch to turn this off because this behaviour of the software is not needed for us. No success so far. Does someone have a hint on what might be the trick? Thanks Stefan

1 1

Varying reports for solution time escalations. what could be the reason
by Katta, Lokesh Katta Subramanyam 04 Jan '10

04 Jan '10

Hi All, I am facing issues in stats for solution time escalation reports. The statistics for solution time escalations in a specific period is varying when we execute report on different dates. For eg. On a Queue <XYZ> there were 10 solution time escalations for the month of September when the report was executed on October 5th. Again when we ran the same report on October 10th the escalations are 5. What could be the reason? Please help. Thanks and Regards, Lokesh

3 6

Problem with "Next ticket state"
by MMoj＠timocom.com 07 Dec '09

07 Dec '09

Hey, Can some one tell my why OTRS "Next ticket state" is per defaul "closed successful" when it is set to be "open" in "Ticket::Frontend::AgentTicketCompose###StateDefault"? Is it a bug? With the Update from 2.4.4 to 2.4.5 today this changed to be "closed successful" but the Helpdesk agents want it to be "open" instead, but it does not work if I define it as "open" int the "ViewCompose". Can some one help me out with a workaround or something? Mit freundlichen Grüßen / Kind regards Markus Moj IT Infrastructure & Services TimoCom Soft- und Hardware GmbH In der Steele 2 D-40599 Düsseldorf Tel: +49 211 88 26 80 14 Fax: +49 211 88 26 70 14 eMail: MMoj(a)TimoCom.com www.TimoCom.com Geschäftsführer: Jens Thiermann, Gunther Matzaitis Amtsgericht Düsseldorf, HRB 34489

4 11

Changing ticket default type to 'Incident'
by patrick.dillon＠aleris.com 19 Nov '09

19 Nov '09

Hello to all, We have defined several basic ticket types, and wish to have all tickets be created as Type::Incident by default. I know this can be manually selected when a ticket is created through the web interface, but where do we change the default option from ' - ' to 'Incident'? I'm assuming this is done in a .pm file somewhere, but I haven't been able to find that entry. Thanks for any guidance, Patrick Dillon Aleris International

4 4

Customer Company as groups ? or group of customers.
by Sarper SARIDAL 18 Nov '09

18 Nov '09

Hi all, I have a question in mind.. For example lets say that i have these customers : 1. katieblack(a)company.org : Company : STARGMBH 2. jameswhite(a)company.org : Company : STARGMBH 3. markyellow(a)company.org : Company : WORLD CO. For the first 2 customers which are from the same company STARGMBH is it possible for katie to see james tickets and james for katie. So if one is out of the company for travel the other can track the records. If there is no such a functionality in the future to have something like this will be great. Thanks & Regards, Sarper

3 2