Thanks for you Reply Kevin.

This would mean that for every search I do, I have to save it and then i can adjust the columns. For searches our agents do on a daily basis that's a good solution. But what about searches that aren't recurrent?

Let's say I want to search a tickets where our order number '540667' has been mentioned (see below). Our Agents would like to see in an instant what the status of that ticket is (open or closed) or maybe when was the last update on one of this tickets.

In the solution mentioned above they would have to save it every time they search an order number through our tickets. I would like to pre change these columns like I can in "Open", "My Tickets" and "Closed".

Thanks ?

a month later

Same here, I want on the Search Results to add the Column STATE (For all the agents on the systems) to take a quick view on the OPEN TICKETS.

+1. The generic search results are less useful if we're specifically looking for a ticket in a specific state (ie. not closed).

5 months later

I have the same problem with 1.12. (Should I open a new thread in that section?) Even for a "basic" search, I should be able to define the default columns. I rely on some fields for at-a-glance ticket information, so it's pretty disappointing to lose that information during searches.

a year later

Hi, I have the same problem. Is there a solution already?

a month later

+1
Same problem.
How to do it for for all employees?

2 months later

I see that you added


// Use the columns of the "Open" queue as a default template
if ($use_template && ($template = CustomQueue::lookup(1)))
return $template->getColumns();

To the code, but when I tried it I get the same, default search columns. I tried putting that snippet at the very start of the function (under function getColumns($use_template=false) {) to try to force it to return the results as early as possible, but no results. I tried just a return of $template->getColumns();, but that just resulted in an error breaking the page.

I'm also currently running version 1.15.2. Any help would be really appreciated.

Edit: I've also gone through the standard columns portion a few lines down. I added a required field under Contact Information called "practices." I tried calling it using various versions of "primary" => 'cdata__practices', as well as user_practices, and just about everything else I could think of.

Thanks so much!

a year later

Also chiming in here, this is really needed.

@kylegp

We use the traditional, hard-coded columns for Advanced Search. As I mentioned above (in 2019) if you want to have Custom Columns, simply save the Advanced Search and you will be able to edit the Columns tab on Queue edit. Otherwise the code is open source and you can customize it to your liking.

Cheers.

a year later

Hello, just wondering if there has been any progress made on the front since the last comment.

    9 days later

    KevinTheJedi There is indeed progress to be made. GiantTinyMidget explained in considerable detail on Mar 28, 2019, (above) why saving the search is not a practical solution. It would be like searching for "muffler bracket" in Google and then saving a bookmark for https://www.google.com/search?q=muffer+bracket in your browser. What good would that bookmark be if later you wanted to search for "alternator"?
    I realize that osTicket is open source, and users are not entitled to anything, but this is a fairly straightforward request that a lot of people have been hoping for. I'm going to attempt to edit the code as sawtooth suggested above. I'll report back on my level of success.

        vermontitguy

        Please, go for it. However, this will not be changing anytime soon (especially not with current legacy codebase).

        Also, make sure you Fork osTicket on GitHub and provide your mod there (in your own fork) as a branch so you can track issues within your own repo and doesn't cloud our repo.

        Cheers.

          Write a Reply...