Okay, great, that sounds like a plan.I'll try them out and let you know how I got on.Thanks.

Hey Chefkeks, thanks for taking a look.Briefly, our mail exchange server had a catastrophic failure a while back. I won't go into details other than to say a team of Microsoft techs couldn't bring it back to life and it had to be rebuilt. It was also, for reasons unknown to me, hosting osTicket over IIS.Anyway, I looked for a recovery procedure on the wiki but couldn't find anything. I managed to recover the database from a backup and setup osTicket again pointing to the database. Other than this, everything appears to work fine.Any other details that would be helpful? I'll provide as much as I can.

Hi all,I'm getting spammed by alerts@domain.com with this error message:

Table 'osticket.ost_draft' doesn't exist<br />

<br />

---- Backtrace ----<br />

#0

C:\inetpub\wwwroot\osTicket\upload\include\mysqli.php(169):

osTicket->logDBError('DB Error #1146', '[INSERT INTO os...')<br />

#1

C:\inetpub\wwwroot\osTicket\upload\include\class.draft.php(91):

db_query('INSERT INTO ost...')<br />

#2

C:\inetpub\wwwroot\osTicket\upload\include\class.draft.php(109):

Draft->save(0, Array, Array)<br />

#3

C:\inetpub\wwwroot\osTicket\upload\include\ajax.draft.php(22):

Draft->create(Array, Array)<br />

#4

C:\inetpub\wwwroot\osTicket\upload\include\ajax.draft.php(199):

DraftAjaxAPI->_createDraft(Array)<br />

#5 : DraftAjaxAPI->createDraft('ticket.note.113')<br

/>

#6

C:\inetpub\wwwroot\osTicket\upload\include\class.dispatcher.php(145):

call_user_func_array(Array, Array)<br />

#7

C:\inetpub\wwwroot\osTicket\upload\include\class.dispatcher.php(38):

UrlMatcher->dispatch('ticket.note.113', Array)<br />

#8

C:\inetpub\wwwroot\osTicket\upload\include\class.dispatcher.php(120):

Dispatcher->resolve('ticket.note.113', Array)<br />

#9

C:\inetpub\wwwroot\osTicket\upload\include\class.dispatcher.php(38):

UrlMatcher->dispatch('/draft/ticket.n...', NULL)<br />

#10 C:\inetpub\wwwroot\osTicket\upload\scp\ajax.php(172):

Dispatcher->resolve('/draft/ticket.n...')<br />

#11 {main}

I'm not sure if this is actually possible and I'm not doing it correctly or if this is a genuine suggesstion but I was trying to add a variable to the department signature.What I'd like it to do is pull the name of the staff member making the response and insert that in the signature.Something like:FirstNameIT Support DepartmentI've tried %{ticket.staff} but that's either the wrong one or it's not possible yet.

Yeah but I think he want's to have a note appear on every ticket whenever a specific user creates one.

You can create a custom field that will be empty for all tickets and only viewable internally by staff. But as far as I know, you can't create a field with pre-populated data (though I reserve the right to be wrong).

Perhaps the options of All, Internal and Organisations. That way the KB doesn't have to be limited to only an individual organisation but can be applied to a specified list of them Organisations. This could be done at the Category level and the FAQ level.

A nice idea. +1Maybe a nice coder will implement it and make a pull request.

Great, can't wait till the API grows.Exciting times ahead.

Could just overwrite the old closed date. It all rather depends on the requirements; if you needed to see all the times the ticket has been opened and closed then you could record of that using the db and creating a table with that datetime information linked to the ticket by a one-to-many relation. I've not looked at the db to see how relational it is, but it would make logical sense to do it that way.

@[deleted] a poor choice of words, by "departments" in this context, I meant a theoretical subgroup under Organization so that users could be "subgrouped" and permissions customised according to the needs of the users and what makes logical sense in the circumstances.

This would certainly be a nice feature.+1

It would be nice if we had a deep level of configuration for this. Perhaps the ability to add deeper levels to Organisations: you could have an organisation containing all the users, and then separate them into "departments" as you choose.Each department could have slightly different permissions as you choose so that members of a Managers department could be see all the tickets of the organisation and perhaps receive notifications when a member of their organisation creates a ticket to be set on an individual basis, whereas the regular users could only see their own.You could also set each department to have a Team Leader who can be set to get notifications when a member of their department creates a ticket and can view all the tickets of their department.It would be nice to have the deeper configuration options.

I haven't had any problems with it not being there yet, but yes, I can agree with the principle that it ought to be there. +1

You could also create a mod that subtracted the difference between the when the ticket opened and when the ticket was closed and add that to a new table in the db.

Hi, just saw this ticket: http://forum.osticket.com/d/discussion//archive and wondered if there is any documentation on creating plugins available yet?

Where is this to-do list? Is there a current concrete roadmap that's been made publicly available?

Hi Guys,Currently, if you store a phone number in this format: +44 (0) 1234 567 890 it will save like this: 4401234567890.Now, I can see why the phone numbers were stored this way (it's easier to validate as a phone number if you just store digits, plus the database can be set to numbers only rather than varchar), and honestly, it wouldn't be a problem if all our offices and clients were in the same country.However, could there be some way to save phone numbers in this format? Perhaps it's possible to compromise by adding a national prefix field?

Sounds good to me.

I think the point is that this is something people would like to see incorporated into the native site rather than something they have to pay extra for from a modding team.