Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

In this Discussion

osTicket v1.10 (stable) and Maintenance Release v1.9.15 are now available! Go get it now

1.10 Stable - Changing Ticket Source

edited November 2016 in Mods and Customizations
I need to chanege the source option in 1.10 stable

I researched past methods to change sources and none seemed to apply to the current version.
I began to read through the code and changed include\class.ticket.php

Lines 142-157:

   // Ticket Sources
    static protected $sources =  array(
            'Driver' =>
            /* @trans */ 'Driver',
            'Mechanic' =>
            /* @trans */ 'Mechanic',

            'Employee' =>
            /* @trans */ 'Employee',
            'API' =>
            /* @trans */ 'API',
            'External' =>
            /* @trans */ 'External',
            'DOT' =>
            /* @trans */ 'DOT',

Moved it back to the server and tried to create a ticket.
The good news - nothing broke; The bad news it prints blank under the new ticket.

Does anyone have any insight into what I need to change to actually include the source entry?


  • Hey chief, 

    I haven't used/played with 10 yet, but in previous versions, it is hard-coded in the include/staff/ticket-open.php.
    They've a new system! ok.

    Looks like you were on the right track, adding that to class.ticket.php should make it available to the via Ticket::getSources() function. So creating a ticket as a staff member should give you all of those options.

    Looks like everything else relies on that or simply the $ticket->getSource() method.. 

    Where are you seeing this blank? In the create/new drop-down or the ticket view, or ticket-edit?
  • Hey ntech,

    I really new to osTicket and was on the same boat as you so don't know if you already resolve your issue or still pending but you can look at this post for the answer.

    It seeing blank when you open the ticket, the Source field is blank and if you look at the DB it is also. That happen if you only edit the class.ticket.php.


  • I haven' checked for this case but i know that they have restrictions on what values can be inserted into the sql, so try modify that.
  • It's probably better to add as a field anyway, the ticket source really has only three options.
Sign In or Register to comment.