Re: [otrs] Making categories of tickets

27 May 2004


      On Monday, May 17, 2004 5:27 PM
Lohmeijer, Martijn  wrote:
...
"Freetext" fields. After configuring a sample freetext field I
noticed that the freetext fields in general remain flat text fields
and that working with drop down boxes is not enforced through the UI.
An agent or customer can simply leave them blank or edit them any way
he/she likes.
Am I overlooking something ?  How have you handled this situation and
/ or what do you do to differentiate calls for different applications
?
You're searching for this, I believe:

    # TicketFreeText                                      #
    # (define free text options for frontend)             #
    # --------------------------------------------------- #
    $Self->{"TicketFreeKey1"} = {
        '' => '-',
        'Product' => 'Product',
    };
    $Self->{"TicketFreeText1"} = {
        '' => '-',
        'PC' => 'PC',
        'Notebook' => 'Notebook',
        'LCD' => 'LCD',
        'Phone' => 'Phone',
    };
#    $Self->{"TicketFreeKey2"} = {
#        '' => '-',
#        'Support' => 'Support',
#    };

    # default selections (if wanted)
    # $Self->{"TicketFreeText1::DefaultSelection"} = 'Notebook';

hth,

Robert Kehl

--
((otrs.de)) :: OTRS GmbH :: Norsk-Data-Str. 1 :: 61352 Bad Homburg
         http://www.otrs.de/ :: Tel. +49 (0)6172 4832388