i've got it working on 1.9.4there'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.4basically 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_assignmentsit 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.

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.

Hi, I have added two custom fields in the ticket. In the Ticket.cdata these fields are called RMS and RIS and I would see them on the main page of the agent (2 new coloumn):scp / index.phpHow do?I have osticket 1.9.4

Hi, I'm trying to display a column in the ticket portion of the agent panel that shows the respective Department for each ticket.  You can view the screen in this image: I posted something about it and I was directed to this forum.  I have downloaded the Mod and it seems to be displaying a Status bar, however I'd like to know how to change it so that it displays Departments instead.  I do not feel comfortable editing the code itself since I don't know php, I'm just trying to set up the service.Currently, this is what I see when viewing my "Modules" :If I could receive some either managing the Mod or editing the code so that I can add a "Departments" column, that would be hugely appreciated.  Thanks! :)

I am new to osTicket, so please bear with me.  I tried installing this version of the better ticket list from https://github.com/rowlandan25/osTicket-Modules/releases/tag/v1.1.07-alpha.1010, it looks like version 1.1.07 alpha 1010, and I get an error when I try to initialize the module via the Modules tab.  All it says is "Unknown setting option. Get technical support.", but I double-checked that everything is correct.  It doesn't seem that the database table is being created for this mod.  Any help would be awesome, as I really want to expand what the ticket list shows.

Well, i've installed this Mod without problem, but now i need to add a new column like Organization or other to main grid.How can do that?? anybody can help? please :-)Thx

Great module!!! Perfectly working :-)

are you using the latest version 1.9.5.1 ?it didnt work for me on the latest version 

Installed on Version 1.9.7 works GREATI had a bit of a problem to get the shape to work but just disabled and re-enabled module and Bingo!!

Is there any incompatibility with osticket 1.9.7? I see it replaces some core files, so am I losing any code updates in these files in 1.9.7?Regards,Marvin M

Just chiming in here about a potential problem with this module in 1.9.7:I am unable to create a new Ticket Status via Admin -> Manage -> Lists -> Custom List The issue is that, when I go to edit the properties on the custom status, I try to save the changes, but the "Ticket Status" drop down (Open or Closed) always reverts to NULL after clicking OK to save the changes.  I'm going to take a look at the code myself, but I'm not a programmer, so if I don't find anything I will report backEDIT:Nevermind.. This appears to be an issue with osTicket itself. Even in version 1.9.4 I am unable to actually create a new custom status due to the Ticket State drop down resetting when I click save.