Webamoeba Ticket System



NOW JOOMLA! 1.5 COMPATIBLE
Feature list
* User Management
* User Groups
* User Agreement
* Rightes Manager
* Ticket Categories
* Ticket/User Assignement
* CSS Editor
* Database Maintenance
* Highlight new and altered tickets
* Email notification
* BBCode, CMS editor, or plain text editor
* Debug Mode
* Search (seperate plugin)
Available in
* English
* Brazillian
* Czech
* Farsi
* French
* German
* Greek
* Italian
* Netherlands
* Norweigan
* Portuguese
* Russian
* Serbian
* Slovenian
* Slovak
* Spanish
* Swedish
* Turkish
You can also create your own translations!
If you are using a version prior to 2.0.8, you should upgrade immediately. The latest release includes a number of security fixes!
Templating and a better default layout would be a future improvement which would earn you my vote of 5/5, but form must follow function and the functions are right on the money. Simple, but right.
I did notice a server time difference, but need to investigate more. It might just be my setting as I recently moved from one time zone to another.
The latest version resolves the issues with dates and times.
Simple to implement and setup, and easy to use for clients.
Would like to see the following added:
* ablity for admin to add tickets
* ablity to edit tickets via backend
* add ticket priority.
I'm trying it out for a school network of a few hundred computers, so we'll see how it handles that.
Of course I'd like to have some extra fields for logging jobs (serial numbers etc. so I can establish an audit trail of issues), but I expect I should be able to hack that in over time.
Great work!!
Ok, so it's not that fancy as the other support systems, however it's simplicity makes it nice, easy to handle/load and with a little design makeup you get a GREAT support system for Free!
Highly recommended!
What I dislike is that when ever someone goes to submit a ticket it goes to reply and reply and close as if they were an admin?
also some form of control on the layout would be nice. I had a real hard time making it work with several templates.
Cons: surely it could be improved, specially for the HTML design.
I was able to install the components easily, but I could not delete any user posts. I also couldn't re-open a closed ticket, or figure out how ticket numbers are generated or used.
I think this has great potential, but is far from being usable in a production environment, unless it is all my lack of understanding (quite possible!).
Took about 5 minutes to install and configure. Great selling point.
I installed it as the documents showed. But then what. How do the users access it to enter a new ticket? Had to figure out that you need to then add a menu item. Set as a component.
Would like to see sub categories. Also seems a bit busy, reduce the amount of unneeded information from the screen.
I added a few categories, and when I entered a test ticket, the categories did not list.
Over all,.. I feel that this add-on has some great potential. I will continue to look at it,.. and use it.
My issues are with how it does things.
I added all 700 users in my joomla site to the ticketing system (why they needed to be added is one of my issues, they exist in joomla that should be enough)
When I logged into the front end as an administrator I found that it was taking a long time to display the page even though the default was to display only the first 5 users.
turned on debug and found that rather than limiting the number of users it was getting the details of all 700 users, and what more after it retrieved those details in 1 query it then proceeded to load the details again for each individual user, and because I was an admin it used not 1 but 2 queries to get the user data. This means that with 700 users this component was doing over 1400 queries to build a list that ultimately only showed 5 users on the page.
All of the front end code seems to work this way.
An initial query to find all of the records from the required table, then another query for each record found to find the data again.
For a large site like mine this means that there are way to many queries being run.
Also the pagination does not work well because as mentioned above it grabs all the data first and then determines what it should display, but there is also to list size parameters for the component
front page tickets and sub page tickets.
Now I can sort of understand that this is so that the front page can have more or less than the rest, however the calculations that it does to determine the pages are wrong
when i changed the system from 5 on the front page to 15 and set the sub page to 30 it showed 50 pages of users when I was on the first page and then only 25 page when I was on the second page
In reality it should have shown about 25 or 26 pages all the time because the first page was 15 and the rest we 30 but it doesnt take the difference between the numbers into account
I would also like to see the ability for admin to reply to tickets in the back-end of joomla (as an administrator that is where I spend most of my time)
Final issue was that there is, so far, 1 short tag used in the front end to display the copyright information, and since I have short tags turned off (as any good Joomla developer should) then the copyright does not display correctly.
FYI - in half an hour I hacked and wrote the display so that rather than 1400 queries to display the list of users in the front end it took only 2 queries. Also from what I can see all of the front end display basically has these same problems, multiple queries (an initial query to get the list of records and then another one for each record) and pagenavigation using all of the records rather than using limits in the initial queries.
ah yes urm hmm er yes.
firstly, you didn't need to add all your users, all you needed to do was enable 'allow all user access'. The reaosn for this is simple, not all sites are necessarily going to want to all of their site users to have access to WATS. This really comes down to waiting for a full J! ACL system.
I'll have to check the pagination.
Your point about the massive number of queries being made is well taken, this definitlety needs resolving. I'm extremely busy (always seem to be at the moment), but I will look into this ASAP.
What's more, it seems that this com_ does not support attachments. Sometimes attachments is good. Why not add it ?
Hi baijianpeng,
You maybe interested to know that all of this is planned for the future. I'm currently involved in a new project (MVCCTC) together we are documenting how to develop good components. Once this starts nearing completion I will add 'custom fields' (which will include attachments) and translations for front and backend :)
It gave me all what I need
Upgrade done smoothly with no errors :)
Thanks for your efforts
The system allows for simple configuration, easy layout control and is feature rich.
james has put a lot of thought into this component and it definately shows. I truly believe that this is one of those components, that is a MUST HAVE for ANY professional website.
Great support from a great guy.
My only suggestions would be to allow non site members the ability to use the ticket system, then it could be used as a Bug tracker of sorts. I believbe that a great extension to this would be to allow admin the ability to take any Q&A, and add them to a special list for an extended FAQ section.
Brilliant piece of work, thanks James for your hard work & allowing users like me to implement into my website!
Happy with outcome.









