The Joomla! Extensions Directory ™

Fantastic component easy to install and easy for work. Only is sad not have a version for Joomla 1.6 . I like to take this project and make the next versions if the owner like the idea

PROS: Simple, can assign groups for multi-user ticket access
CONS: Can't manage tickets from backend (even as admin), no attachments can be added to tickets

This extension solved a problem I had with needing a help desk type of ticket system along with a project desk type of system in that it allows the users in a group to see and update tickets as needed.

Well this may sound strange but if this extention was female I would marry it. It looks super thanks to the ability to alter the looks via CSS in admin panel, which is perfectly commented!. It does what you want when you want.
I will admit that at first I was pulling my hair out with it, but after reading the documentation it was so easy to use and set up I didnt even try any others.

I have yet to try the support for this extention as I have not had any need to yet. But going by the extention itself I will say they are going to be good!

Shame there is no option to rate this as 6 stars!

This would be a GREAT system if the following were addressed:

1) There is no way to see which tickets HAVE NOT been assigned to anybody. This causes tickets to grow old and not get addressed. The admin must constantly sort through the tickets to find unassigned tickets.

2) There is no way to change the category after you create a ticket. It's super easy to forget to assign the category then there is no way to fix it except to go into the database and edit it by hand. We need a way to change categories on other fields after the ticket has been created.

3) There is no reporting whatsoever - It would be helpful to see all tickets on one table with the ability to sort by headings such as date (so you can find old tickets that go forgotten or are not assigned), or sort by assigned rep (so you can see which reps are overloaded and which have room for more tickets), etc.

If these issues were fixed, this could be the #1 ticketing system..

I like the look of this extension from it's screen shots and listed features.

Unfortunately, because most of my customers do not create accounts on my site, I couldn't use this extension, because it does not allow unregistered users to submit tickets.

Setting the "All User Access" to yes, only opens the system up to registered users. Registered users should be allowed to submit tickets by default, and Admins allowed to open the system up to unregistered.

If this feature is ever enabled, I will revisit this system, as it seems pretty robust.

Does the job, could be tidier format but for a free, uncomplicated extension it works well.

Thank you for creating a working system. It just works.

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.

I love this component. It is very reliable but there is an issue with the time/date displayed in tickets. If your server has a different timezone you cannot change the setting from global configuration, and your tickets shows wrong time.

Having moved from V2.0.8 to V3 of this component, I'm pleased to note the component is now 1.5 compatiable and well supported in their forums.

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.

It did everything the manual promised. Very quick and easy to install. I notice that some of the negative comments in the reviews on the system seem to be attributable to the operator failing to RTFM.

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!!

the frontend is very busy, sloppy and all runs together. It also needs to be able to have files to be uploaded. And it pops up all kinds of stuff, like organization, user, admin... who needs that. Its too sloppy. I uninstalled and I will keep looking.

Thanks for this component. It's great & totally useable.

I' using joomla 1.0.13. I douwnload this product and only get a blank screen. The download page are on joomla and maybe if we can acsess to older version It will be great. Probably that the new version have compatibility with Joomla 1.5 but it's a mess with older platform.

We have been using the WebAmoeba ticket system for a while now on our site for supporting our customers, and I have to say that it simply DOES the job!

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!

First of all I like the program .

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.

Pro: you can add a help desk / ticket system in your Joomla site, with an easy installation and configuration, and also for free!

Cons: surely it could be improved, specially for the HTML design.

I am a total newbie to Joomla, but I am not aware of "rites" being part of this environment. Sounds like paganism to me. I would have thought that "rights" are perhaps more appropriate?

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!).

I printed out the dox... who does that anymore.

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.

Before I get to the bad I should say that overall I like this component. A pretty good effort at a ticketing system.

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.

I am testing this on my local server. It works well. But the problem is I can't translate the backend since those words was not included in the language file.

What's more, it seems that this com_ does not support attachments. Sometimes attachments is good. Why not add it ?