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

A better ticket list!

123578

Comments

  • Hi guys.

    can i use the status mod for the 1.7 version ?

    Thanks for all.
  • Hey there reyhykary,

    This specific module is not available for the 1.7 version.  However, I know at one point there was a post for a status mod for 1.7 (but I think it was on the old forums).
  • thanks rowland, i was confused, because the mod is posted in 1.7 forum.
    Hey there reyhykary, This specific module is not available for the 1.7 version.  However, I know at one point there was a post for a status mod for 1.7 (but I think it was on the old forums).

  • Yeah, maybe ntozier will move this to the right forum.  There wasn't a 1.8 forum when  1.8 was released, this was just the "Current version" forum!
  • edited April 2014
    Now my osticket is in spanish with another mods too. What can i see, the language pack is not full finish for the newer version. I have no problems with the native language , but the people in my company yes.

    i'm already translating directly all the titles, menus, etc. It's a hard work, i need to find some things for change to spanish language. The client side is 90% done . I put some files:
    info.png
    1021 x 461 - 29K
  • I had the problem that the advanced search form was not working with the status. (i'm on 1.8.0.3)
    now it works. I was not able to filter by the status (after the status has changed once).
    perhaps someone else has the same problem.

    i added a sql query to the file "Web Directory\include\class.ticket.php":

        //As long as results were returned, update the status.
        $sql = "UPDATE ".FORM_ANSWER_TABLE." SET value='" . $item_value . "', value_id='" . $status_val . "' WHERE field_id='".$field_id."' AND entry_id='" . $entry_id . "'";
    $ost->logDebug("Status Update",$sql);
        $res = db_query($sql);
    $sql = "INSERT INTO ".TABLE_PREFIX."ticket__cdata SET field_".$field_id."='" . $item_value . "' , field_".$field_id."_id='" . $status_val . "' , `ticket_id`=".$this->getId()
              ." ON DUPLICATE KEY UPDATE field_".$field_id."='". $item_value . "' , field_".$field_id."_id='" . $status_val . "'";
         $res = db_query($sql);

    After this update, you have to update every status. else the system still can't filter it.
  • Hi,

    Does this mod work for v1.9.0? Would love to use this in my system :-)

    Thanks
  • Hey there bcv,

    I just got back from vacation and will get it deployed for v1.9! I will keep you posted.

    Andy
  • Thanks a bunch!
  • I would like to be informed on this issue.
  • Thanks, and look forward to updates....
  • Hi, I started exploring Osticket with 1.9 version, is there a chance that this module can be set on 1.9? Where can I find it if this already exists? Thank You!
  • @Cabat the mod author rowlandan25 has not posted a version for 1.9 yet.
  • Hi there. Im currently on version 1.9.2 .. And i found your topic buat it was kind of outdated.. version 1.8.1 ?? And rowlandan25 last reply on here was nearly 2months ago in May.

    Is the development already stop? Im afraid i will need this ticket status mod very badly! T_T
  • Good morning everyone,

    First off, I would like to apologize for not being active the past couple of months.  Unfortunately work is busiest for me during the summer and I have not had the time to sit down and get the newest version of ticket status out.  I am going to begin development again and get that out soon!  When I do, I will start a new discussion in the 1.9 forums and post a link to that discussion here.

    Once I get the update done, I will be looking for some testers to so that I can find any issues with it!

    Andy
  • Good morning everyone, First off, I would like to apologize for not being active the past couple of months.  Unfortunately work is busiest for me during the summer and I have not had the time to sit down and get the newest version of ticket status out.  I am going to begin development again and get that out soon!  When I do, I will start a new discussion in the 1.9 forums and post a link to that discussion here. Once I get the update done, I will be looking for some testers to so that I can find any issues with it! Andy
    thank you rowland. look forward to contribute on your thread :)
  • Hey everyone,

    I create a new thread for the 1.9.3 version of this mod.  Take a look: http://osticket.com/forum/discussion/78493/add-statuses-to-your-tickets
  • @rowlandan25 

    Just wondering if this is now included in release 1.9.4?  If so, I don't seem to see the status in the "open ticket" listing.  Is there anything I'm missing?  How can someone on version 1.9.4 achieve the "Status" view of open tickets?

    Thanks for the reply.
  • edited November 2014
    same for me! ver 1.9.4 (c18eac4) plugin(Language (Portuguese))only appear  total openticket(0) close(0).tks
  • i've got it working on 1.9.4

    there's quite a few differences in there. 

    i made no changes to any files which don't already exist in 1.9.4, just uploaded those files to the relevent folder.

    for files that already exist, i run a diff on the mod files, comparing them to the unmodified 1.9.3 files to find out what the actual mods were.

    and copied them into the 1.9.4 files, making changes to match the new syntax where necessary, it's obvious what these changes need to be when the mods are pasted in.

    the big problem was the changes in table/field names in 1.9.4

    basically change:                
    .' ,status.statusName as statName, status.colorBG as bg, status.colorFG as fg, status.colorBD as bd';
    to:
           .' ,stat.statusName as statName, stat.colorBG as bg, stat.colorFG as fg, stat.colorBD as bd';

    and 
             ' LEFT JOIN '.MOD_STATUS.' status ON msa.statusId=status.id';
    to
             ' LEFT JOIN '.MOD_STATUS.' stat ON msa.statusId=stat.id';

    in  /include/staff/tickets.inc.php
  • I am working on upgrading the mod to version 1.9.4 and hope to have a working version out by the end of the week.
  • is there any reason for holding onto the previous statuses? 
    ie isActive = 0 in mod_status_assignments

    it would make the table very large quite quickly, especially on a busy helpdesk.

    i would suggest when updating the ticket status in that table, it then deletes any rows where isActive = 0.

    i've found that leaving them in there means it displays different statuses for a ticket when ordering by tstatus ASC than it does ordering by tstatus DESC.
  • edited November 2014
    I am already working to remove this table, and will be removed in the next update :)   It was meant to be temporary till I added an internal note for status changes.
  • cool.

    i have a couple of suggestions, some of which i'm sure you're already planning, or have at least considered.

    having statuses like:  scheduled, client/customer update. 
    where scheduled using the due date, which i believe (not tested it yet) sets out an stale ticket alert, and sets the ticket to overdue using it's own ticket status. 
    i'd like to see the mod ticket status (tstatus) get changed to overdue at the same time. 

    i'd like to see this happen when the SLA period expires as well. 
    (it may already, as i said, i've not tested it yet)

    when a customer responds, a new message alert is sent out, i'd like tstatus to change the tickets state to client/customer update. 

    so basically it responds to events, rather than having to manually change the status.


    probably simple enough stuff, just not had a chance to look at the code for it, and i'd imagine most people would want it.

  • Build 1007 (which I never got to the point to release before 1.9.4 came out) has started those suggestions.  I have pre-defined locations (when a ticket is opened, when a ticket is assigned, and when a ticket is reopened) that the status is updated.  I am looking to expand on those, and your options are great places to start. 

    The overdue via SLA period should not be difficult to do as I just need to find where this is handled.  Having a scheduled status also should not be too difficult, again, I just need to find where it is handled.

    I looked into doing the responses and that one is more tricky.  I was having difficulties determining the response type between an agent posting a response and a client/customer posting a response.  I just having to look some more and see if there is an easy fix.

    Thanks for the suggestions.
  • Build 1008 of my module is ready to go (you can get it here: https://github.com/rowlandan25/osTicket-Modules/releases/tag/1008).

    If you run into any issues, please be sure to post them on GitHub so I can take a look.  I have tested this pack on a fresh osTicket v1.9.4 install and I have also tried it on an osTicket v1.9.3 install with my Build 1006 module pack.  Both of them worked perfectly.  Please, make sure that you create a copy of your web directory and database before installing any module.

    If you would like to see anything added, please feel free to submit that on GitHub as well and I will look into adding it.

    Enjoy!

    Andy
  • Hi this is not working for us, it shows the ticket status in now but the colors will not change no matter what they are set to and in the custom list properties the variables are all set to 15 which conflicts.
  • Hi Wizard123,

    Thanks for the post.  This issue has been reported on GitHub and I already have a fix for it.  I am finishing up fixing a couple more bugs and then I will have another update posted this morning.

    Andy
  • Great thank you very much.
Sign In or Register to comment.