July 2005 - dev - OTRS mailing lists

PATCH - Oldest Queue configurable HTML Tag
by Alexander Koch 14 Jul '05

14 Jul '05

Hello, First, I'am not an developer and I'am using OTRS not long. So I don't know if this patch is usable. I don't like the <blink>Oldest Queue</blink> and I don't want change source code after each update. So here two patches. I hope everyone understand what I tried. Perhaps some developers can put it in the right naming convention. And improve it. It is only a dirty hack with that I can live. My first idea was to make an option which you can set to blink or bold and then to make the right HTML tags, but I don't find the right place for "make <b> for bold and <blink> for blink". So you must put the right tag in the option itself. But this makes some unbeautiful possibilities ... Regards, Alex -- Alexander Koch, mailto: ak(a)ilk.net ILK Internet GmbH, Akademiestrasse 25 - 27, D-76133 Karlsruhe Tel: +49 (0) 721 9100 0, Fax: +49 (0) 721 9100 191 http://www.ilk.net

1 0

AW: [dev] Add TicketKey and Value in Postmaster/FollowUp?
by Kaiser Dr., Thomas (LfStaD) 08 Jul '05

08 Jul '05

Hi Martin, Thanks for the fast reply. There are two ticket systems. One for us and one or more for the operating people in different organisations. There will be tickets, which are created on one side and forwarded for further processing to the other one. Since there may several interactions for one ticket the goal is to keep track on both sides in the tickets. Each ticket system keep track of the Ids in the other system. The general mechanism for hand-overs is email. E.g. a ticket is created in otrs and during the processing a hand-over to the operating is needed. Therefore a ticket in HP OV ServiceDesk has to be created via email. HP OV ServiceDesk confirms the creation with an email with its ID and keeps the OTRS ID. Any further hand-over of tickets in both directions includes allways the ID of the other system. E.g. OTRS has two methods to use, "NEW description" and "Update ID". For all update the OV-ID is needed. We changed AgendCompose.pm to allow us to modify subject and structure body for this messages. An example: OTRS has a ticket id 10223344, this will be forwarded to HP OV and creates a ticket there. HP OV replies back with the otrs ID 10223344 in the subject and its OV-ID 1876, which will be kept in the otrs-ticket. Lets assume the ticket will be handed over to otrs again and after some processing the ticket is put back to HP OV again. Then the OV-ID 1876 is needed to prevent an opening of another ticket. This can also happen vice versa. Thanks and regards Thomas Kaiser -----Ursprüngliche Nachricht----- Von: Martin Edenhofer [mailto:me@otrs.de] Gesendet: Montag, 4. Juli 2005 23:12 An: Development community of OTRS.org Betreff: Re: [dev] Add TicketKey and Value in Postmaster/FollowUp? Hi Thomas, sure, there would be a way to implement TicketFreeText updates in FollowUp.pm. But at first (maybe I have a other idea) tell me a example/scenario and I'll think about. :-) PS: Thanks for the gpg bug report. :) Martin -- ((otrs)) :: OTRS GmbH :: Norsk-Data-Str. 1 :: 61352 Bad Homburg http://www.otrs.de/ :: Manage your communication! Kaiser Dr., Thomas (LfStaD) wrote: > Hello, > > We are investigating in an mechanismen to couple HP ServiceDesk and > OTRS. One problem is the ticket reference on both sides. We agreed to > keep each others ticket id and do update. We used the ticketkey and > ticketvalue free fields for this. Unfortunately an update of ticket > free fields is not included in FollowUp. Is there a possibility to > implement this in the FollowUp.pm or any other ideas? > > Regards > > Thomas Kaiser _______________________________________________ OTRS mailing list: dev - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/dev To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev

2 1

Add TicketKey and Value in Postmaster/FollowUp?
by Kaiser Dr., Thomas (LfStaD) 07 Jul '05

07 Jul '05

Hello, We are investigating in an mechanismen to couple HP ServiceDesk and OTRS. One problem is the ticket reference on both sides. We agreed to keep each others ticket id and do update. We used the ticketkey and ticketvalue free fields for this. Unfortunately an update of ticket free fields is not included in FollowUp. Is there a possibility to implement this in the FollowUp.pm or any other ideas? Regards Thomas Kaiser

3 2

Fwd: OTRS 2.0 Beta 4 (Klong Jark Beach) Released
by Bryan Fullerton 05 Jul '05

05 Jul '05

Regarding the announcement message for 2.0 Beta 4... ---------- Forwarded message ---------- The OTRS Team is pleased to announce the release of OTRS 2.0 Beta 4. [snip] o added ticket free time feature - take care, you need to alter the ticket table: ALTER TABLE ticket ADD freetime1 DATETIME; ALTER TABLE ticket ADD freetime2 DATETIME; [snip] -------- The above probably works great for MySQL, but if you're running PostgreSQL you need TIMESTAMP instead of DATETIME (or at least I did, running PostgreSQL 7.4.8). Other than that, Beta 4 is all good so far. :) Thanks, Bryan

1 0