I love the idea of the custom columns in 1.11, but I am having an issue with how it is working. I work in a school district and one of the fields we have users enter to make a ticket is "building", so we know what building the teacher/user is entering the ticket from. Sometimes though, tickets will be made via "email" and the building field will not be entered because they made the ticket by emailing our helpdesk. In those cases, I like to update the ticket to reflect the building after the ticket has been made. The problem I am having is that I have created a custom column that uses the "building" field so we can sort by what building the ticket is from, but the "building" column is empty in the case where someone emailed to make a ticket and I have updated it after the fact. Even after updating the ticket with the tickets correct "building", the column data remains empty as if there is no connection between the updated "building" field and the one the user selects when making a ticket? For some reason it only shows when a user makes a ticket through the ticket form on the helpdesk site. I was hoping that a simple update to the ticket and adding the correct building on our end would fix this. Is there any way I could get these fields connected to show in the column after a update? Thanks for your time and help,

Dustin

I believe that this is a "problem" in the fact that to speed up search (queue) display results the ost_ticket__cdata table is used to display results. Since you have edited the ticket, it doesn't push the results to the cdata table and they would not show up until that table is dropped and regenerated.

I'll ping a dev just to make sure that I am correct.

    @djolson

    I cannot reproduce this issue with the latest pull from develop-next and PHP 5.6.

    My thinking is that your CDATA table is not recreating itself with the pertinent data. Check your Apache/PHP error logs for any related errors.

    Cheers.

      7 days later

      KevinTheJedi

      Thanks for the response. I looked in both logs and there isn't much in there. I have php version 7.2, could that be an issue?

        @djolson

        No, I also have another instance running PHP 7.2 and 1.11 stable and this install is just fine as well.

        PHP Support
        1.10.x => Supports up to PHP 7.0.x
        1.11.x => Supports up to PHP 7.2.x

        Cheers.

          KevinTheJedi

          ntozier

          Just an update, there was nothing in the logs that indicated a problem (as far as I could tell), but I decided to update MYSQL from 5.5.62 to 5.7.25 in the hopes that would fix the issue. After updating, I just had to go to the "building" field in the tickets where it was not showing up and change it, then put it back to the correct one and it started showing up. So the fix seemed to be updating MYSQL.

          Dustin

              Write a Reply...