PHPJunkyard support forum

Hi Mike,

First of all, A HAPPY NEW YEAR TO YOU AND THANKS a lot for the NEW layout. I looks verry nice

I have some questions to you.

1. Is it possible to disable the due date function in Mods-for-Hesk, we have "use it" in 3 month now. And we have decided we not need this function in this program. So i will like if it was possible to make a checkboks in settings, where we can enable or disable this function in the program.

2. About the tickets detalis, when i look on the detalis - is it possible to add the audit log in to the ticket history in the same ordre where is been add to the case. So we can see when a status on the ticket is changed and if the category has been changed. I will also, do that the customers can see everything a 1 place. See the pictures

https://www.dropbox.com/s/lymzn31331twk ... 9.png?dl=0
https://www.dropbox.com/s/2qp1ucvll7n9n ... 9.png?dl=0

3. The layout in the backend, will it also come to the frontend, to the customers?

jones wrote: Is it possible to disable the due date function in Mods-for-Hesk, we have "use it" in 3 month now. And we have decided we not need this function in this program. So i will like if it was possible to make a checkboks in settings, where we can enable or disable this function in the program.

Due date isn't required, so for now you can just leave it blank. Not sure if I'll add an option to enable/disable it or not. It doesn't really hurt for it to be there, but I understand that it can be annoying if you don't need it.

jones wrote: About the tickets detalis, when i look on the detalis - is it possible to add the audit log in to the ticket history in the same ordre where is been add to the case. So we can see when a status on the ticket is changed and if the category has been changed. I will also, do that the customers can see everything a 1 place. See the pictures

There's one major issue preventing me from doing this: the ticket history for each ticket is stored in one column in the ticket table, with the entire HTML markup of the ticket history section stored. This makes it practically impossible to add this into the main ticket 'timeline' view because the ticket history would have to be parsed. However, if the user changed this in any way, the parsing won't work. One possibility would be to have newer tickets use a better ticket history system that doesn't store the entire HTML, and also allows for the history to be properly translated.

jones wrote: The layout in the backend, will it also come to the frontend, to the customers?

Not sure yet. The template is mainly designed for administrative areas, so I only handled the backend. If the new template is liked by the community, I may look into moving this to the customer frontend as well. No guarantees though