SupportTrio 3.0 development has begun….
We recently started work on SupportTrio 3.0. Version 3.0 will be a major update to the SupportTrio Help Desk product.
We will be incorporating hundreds of changes and additions including such things as:
- Rewriting the majority of the backend code
- Improving the speed and responsiveness of the entire application
- Leaving 99% of the source code unencoded
- CSS Based admin/public interfaces
- Escalation system
- SLA Management
- External Login Sources
- Much more….
While we have our development plans - we still want to know what you want to see in SupportTrio 3.0.
Let us know what you want changed, what you wish was added, general feedback & comments, etc… Your feedback is greatly appreciated and will be taken into consideration for SupportTrio 3.0.
Hello,
when will this major Update released, at the End of the year?
Regards from Germany
heiga
We expect the beta to be available sometime around the end of the year.
We are looking to have the beta released sometime around the end of 2008. Just let us know if you have any other questions!
Thanks for the info Jason. I love SupportTrio and with new features e.g. SLA and Escalation Management it is great product. At the end of the year, is the beta public?
Regards from Germany
heiga
We expect the beta sometime around the end of the year (but do not have any definite dates/timeframe at this time)
It will begin as a private beta and then will be available to all clients and to all trial users.
Search for closed tickets needs to be improved.
You could add :
- search by date (ticket opened or resolved or closed) or between 2 dates.
In main admin page, sender’s e-mail only appears when mouse-over ticket number.
sender e-mail should be a displayable (and sortable) field to display tickts in main amdin page.
Print tickets :
Each week, we need to print the still opened ticket list. For now, there is no great printable version to see tickets details.
Thanks for the feedback - we are planning some significant changes to viewing lists/searching tickets. Just let us know if you have any other suggestions!
For each department, subject of ticket should be either mandatory or not
When using custom fields in tickets, one could be chosen as ticket subject
in think it will come with sla but we never know
each ticket should hâve a due date and time
And tickets should be sorted and filtered by
This.
Another idea: a way to link tickets. For example
A ticket can lead to create 2 “child” tickets and
The main ticket will be closed when the children
Tickets are closed too