Hi,
our client wants to send reports automatically on regular basis to our ticket system. The foreign system doesn’t know about the corresponding ticket number in OTRS, but has own identification numbers of the cases.
Is it possible to let OTRS sort the incoming mails into the corresponding ticket? E.g.
· First appearance of a foreign number creates a ticket
· Following references to the foreign number append the article to the existing OTRS ticket
It’s possible to modify the Mail headers (I think). So I thought about the following possible solution:
· Insert a mail header X-OTRS-TicketNumber
· In Postmaster Mail Account definition enable “Trusted”
· OTRS automagically respects the foreign number
I think that’s Utopia, isn’t it? Are there any other ways? Do I have to modify the sources to let OTRS recognize the foreign numbers?
Regards
Jan Dreyer
IT Administrator / Operations Team / M-IT OMS
Hi, our client wants to send reports automatically on regular basis to our ticket system. The foreign system doesn't know about the corresponding ticket number in OTRS, but has own identification numbers of the cases. Is it possible to let OTRS sort the incoming mails into the corresponding ticket? E.g. * First appearance of a foreign number creates a ticket * Following references to the foreign number append the article to the existing OTRS ticket It's possible to modify the Mail headers (I think). So I thought about the following possible solution: * Insert a mail header X-OTRS-TicketNumber * In Postmaster Mail Account definition enable "Trusted" * OTRS automagically respects the foreign number I think that's Utopia, isn't it? Are there any other ways? Do I have to modify the sources to let OTRS recognize the foreign numbers? Regards Jan Dreyer IT Administrator / Operations Team / M-IT OMS
--------------------------------------------------------------------- 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
-- Perl / OTRS development: http://perl-services.de OTRS AddOn repository: http://opar.perl-services.de
Hi Renée,
thanks for your answer.
The installation I was referring to has 2.4.11 (upgrade is planned), but either with 3.X I have no idea how to link the incoming articles referring to the same case to ONE OTRS ticket via dynfields L
Gruß
Jan Dreyer
IT Administrator / Operations Team / M-IT OMS
I think that’s Utopia, isn’t it? Are there any other ways? Do I have to modify the sources to let OTRS recognize the foreign numbers?
I would do this outside OTRS. If you control the mail server that receives mail for OTRS, give the client a specific alias for the automated reports and make sure their ticket number is in the Subject line. Write a script that extracts the subject line, parses out the foreign ticket # and looks it up in a database table. If not found, make an entry, and use the SOAP interface to create a ticket in OTRS. Capture the ticket # and put in the database table. If the foreign ticket # IS found, append it to the OTRS ticket # recorded in the database table.
No OTRS magic required, and no additional configuration to carry over to the next version of OTRS. Also pretty much transparent to the client, and can be easily replicated for multiple clients.
Hi David,
your solution sounds easy and I think I would be able to write such a script, thanks!
But:
On one hand I don’t like the idea of spreading this work away from the OTRS, on the other hand I _don’t_ control the mail server.
I _could_ do a fetchmail/procmail solution though, if nothing else works.
Regards
Jan Dreyer
IT Administrator / Operations Team / M-IT OMS
Von: otrs-b...@otrs.org [mailto:otrs-b...@otrs.org]
Im Auftrag von David Boyes
Gesendet: Dienstag, 15. Januar 2013 16:47
An: User questions and discussions about OTRS.
Betreff: Re: [otrs] respect foreign ticket IDs
I think that’s Utopia, isn’t it? Are there any other ways? Do I have to modify the sources to let OTRS recognize the foreign numbers?
Hello Michiel
Aaaah, you are right! That sounds exactly like what I’m looking for. Let’s see if our client is willing to do a subscription then …
Regards
Jan Dreyer
IT Administrator / Operations Team / M-IT OMS
On one hand I don’t like the idea of spreading this work away from the OTRS, on the other hand I _don’t_ control the mail server.
I _could_ do a fetchmail/procmail solution though, if nothing else works.
Yeah. I would do this outside OTRS because it’s really a translation function between OTRS and something in the outside world. Neither OTRS or the outside world really needs to know about the translation process (and probably shouldn’t in the long run for scalability), and coding dependencies into OTRS for this kind of stuff always tends to be a pain to unwind later when/if the exception customer goes away. Fetchmail/procmail would be a good route to go for implementation if you can’t control the mail server – I tend to like to do stuff like this in /etc/aliases so it’s easy to find and migrate later, but c’est la vie.
Having a ticket id mapping exit (disabled by default) in the base OTRS postmaster code would be worth submitting as a suggestion, though. Or model it on the Nagios integration package – hmm… what if you tinkered with the Nagios integration package and supplied a different regexp that could recognize the incoming reports from your foreign ticketing system? That might work (haven’t tried it, but in theory all the code is there to create/match/close incoming tickets based on a pattern).
Neat! Haven’t encountered that one before. Should have figured that the OTRS folk had encountered this before... 8-)