- Edited
It would be great to be able to generate a report on any data within the ticket even the custom form data as well. This may already be a feature but I'm just posting here in case it is not.jsmith773
It would be great to be able to generate a report on any data within the ticket even the custom form data as well. This may already be a feature but I'm just posting here in case it is not.jsmith773
Hi, I am running 0.9.6 and have installed the .phar file in the include/plugin folder. Once I've enabled the plugin and change the storage location in settings I treid to attach a file to a ticket but received and error. The error is very general something to the affect of "Error(s) occurred please try again". I tried looking at some logs in the SCP however no logs are generated. When I look at the file folder on the file system (which is writeable via www-data) I see that files were added to the folder for example the name of a file being "oe1jEGar7zflvm0JKRna9bPvzq0WmFh4". If anyone has run into this please help me get around what seems to be a simple issue. Thanks.
Choosing Department
Is there away that the department that the ticket gets routed to can be changed? Maybe this can be something that is input by the support engineer? How is this handled currently?
Api Key IP address
I was able to get this working based on hanspnilsson instructions. Can an API key be generated for a range of addresses or for any address?
I'm currently running Osticket on Ubuntu 12.04.02 LTS and I have everything setup for Osticket 1.7ST. I just recently started using the Knowledge Base feature and I noticed that every time I add or update an article they all have the same timestamp. They all say "Last updated Sun, Mar 31 2013 12."
I'm not sure where to troubleshoot this as there aren't any logs as far as I am aware of.
What OS are you running Osticket on? Ubuntu, Windows, something else?
@jsmith773,Each ticket has a department id (dept_id) so you could include that in the SQL query. Say you only wanted tickets with a dept_id of 1 (note: they are stored as numbers in the database!) you would edit lines 22-26 (the SQL query) by adding whats in red below:
$query = "SELECT $columns
FROM ost_ticket
WHERE status = 'open' AND dept_id = '1'
ORDER BY created DESC
LIMIT 0,$limit";
You can look up the number to department name relationship in the ost_department table either by browsing it or running a SQL query like this:
SELECT dept_id,dept_name FROM ost_department WHERE ispublic='1'
I ran the query on the database and found the correct number for each department. I then edited the correct file and modified the correct line. When I do that the list disappears on the front page and doesn't display anything.
Great MOD
This MOD works very well and will be very useful. Is there a way to display which department the ticket came into and limit tickets to only certain departments to be displayed? I'm not an expert but I would imagine that it would require a pull from the database on the department field and set to only match on specific departments. I guess it would be similar to how you are pulling only open tickets.
Clients can not view ticket status after mod
I just realized my clients can not view ticket status after this mod. I have combed through the files and can't seem to figure out whats wrong. Please help!! They can log in but nothing shows up expect the the client information. None of the added notes show up or the information in the field that I added.
Thanks
Thanks a million this has really helped me out
This mod looks great, but I am not having much luck in getting it to work. When I click the print button, it simply prints the webpage. Any thoughts?
I have the same problem what permission did you have to change it to and was it for the print.css files or some other files? if so i tried with no luck please help.
Adapting this code for the client side
Hi has anyone one adapted the code for the client side? I tried using the same code however I only get a blank white page. Any help would be appreciated.
PS Thanks a million the code works flawlessly on the scp side.