URL to accomplish a search by Agent

mlandis

Hi,I'm brand new to OSTicket, and got it set up and working fine! One capability that I would love to see though is some way to be able to craft a URL to do certain searches, especially by Agent.For example, you can build a URL for a general search - just put your name like fred+flinstone in the URL here for agent+nameosticket.montreat.edu/scp/tickets.php?a=search&query=agent+name&basic_search=SearchThis searches for all tickets and does include the ones assigned to the agent. But it would be nice to be able to search for specific "advanced search" parameters including agent name, status, help topic, etc. That way I can pre-build URLs for our team to get to sub-selects of tickets.I haven't yet dug through the code to see, and unfortunately the advanced search, when it does find something, doesn't seem to put the search query string variables in the link when you click on "view" to see how it crafted the search to start with.(I think I am using 1.9 - I pulled it from git, and the version is 1.8-git, which from what I can tell is actually some variant of 1.9, but I can't actually seem to figure out what version of osticket I am actually using)

Chefkeks

I see what you mean - the default search ist easily customizable.The advanced search always uses some id, but as far as I can see it seems to be the same id for the same search again and again, Maybe you can search the code to get what's behind that id to find a solution.Just for the record, the default and advanced search for the keyword "test" to see the difference:Default: /scp/tickets.php?&a=search&query=test&basic_search=SearchAdvanced: /scp/tickets.php?advsid=42bd72e2223d7ace3e0321c44756a4b7

mlandis

I think that ID is probably some sort of session token, and that the view results query data is submitted by POST instead of on the query string. I haven't gotten in to the code to see if query string variables will work, or what their names are, but when I get some time I'll look in there and see what's up. The fact that the advsid value is the same no matter what search you do definitely suggests the "view" link posts data back to the server instead of being encoded in that hexadecimal string. That's helpful to know.I'm hoping someone has a quick answer that might have used that sort of thing before.Thx.

ntozier

I see what your suggesting, and I think that its a neat idea. (I've done that sort of thing with google before.) But how would you make it secure?