Anybody now of a module for customer support tickets?

You could probably build this pretty easily with cck, views, rules and one of the access control modules or og. There's also a brand new module i haven't had a chance to look at yet: http://drupal.org/project/jobtrack.

_{===
"Give a man a fish and you feed him for a day. Teach a man to fish and you feed him for a lifetime." - Lao Tzu
"God helps those who help themselves." - Ben Franklin
"Search is your best friend." - Worldfallz}

there is also http://drupal.org/project/storm which could do similar things.

However, all the modules i've seen so far seem to be trying to solve too much of the problem and end up re-creating exsisting drupal functionality instead of using the exsisting modules. E.g. notification systems or group systems.

I would defiantly take a look at using OG + a few other modules to create a bespoke system.

I had originally installed Storm which is great but it's more of a project management solution so I now have Jobtrack which I like because of it's simplicity however it's not great for reports in terms of how long tickets have been open etc.

If anyone else has ideas I'd be grateful?

d

Hello,
I am trying to do the same thing.
I am using these modules:
- tac_lite + content_taxonomy: Controls who has permission to which taxonomy terms, maybe in you case "taxonomy == clients". With the content_taxonomy, you have the taxonomy term as a cck field, which integrates with views and tac_lite. I control the access permisions per user, so each user has access permissions to one or many taxonomy terms (companies).
- content_access + node (core): Controls who has permission to which "Content types". I control the access permissions by rol. So each rol has access to create, view, edit or delete some content types. Here I´ve set "Give content node grants priority: -10". This way tac_lite permissions will be taken in account before content_access permissions.
- content_permissions (core): You can grant some permissions based on the CCK field.
- comment_cck: This works as a "ticketing" system. Now I am checking if this integrates with tac_lite and content_access modules.

Hope this helps.

http://drupal.org/project/casetracker

http://drupal.org/project/support

Hi all,
I´ll put together all the information that I´ve gathered.

List of modules
• Organic groups: http://drupal.org/project/og
• Storm: http://drupal.org/project/storm
• Jobstrack -> Support: http://drupal.org/project/support.
  Here you have "Strom vs. Jobstrack" Article http://forum.civicrm.org/index.php?topic=8311.0
• Casetracker: http://drupal.org/project/casetracker

My finally choice is the combination of modules that I have commented before (in this thread) plus the calendar and date module to track my issues with a calendar. I´ve choosen this combination because it gives me more flexibility.
The only problem that I´ve found is the calendar that I´m using. It conflicts with the permissions, but only when I display the calendar when I am editing or creating a node that is using it. So I´ve restricted the Calendar block, to not be shown if this condition exists -> node/*/*

I am testing it, but it looks that it is working fine... so far.

Hello,
I have been doing more testing, and not everything is working as I expected.

Hello,
I am trying to do the same thing.
I am using these modules:
- tac_lite + content_taxonomy: Controls who has permission to which taxonomy terms, maybe in you case "taxonomy == clients". With the content_taxonomy, you have the taxonomy term as a cck field, which integrates with views and tac_lite. I control the access permisions per user, so each user has access permissions to one or many taxonomy terms (companies).
- content_access + node (core): Controls who has permission to which "Content types". I control the access permissions by rol. So each rol has access to create, view, edit or delete some content types. Here I´ve set "Give content node grants priority: -10". This way tac_lite permissions will be taken in account before content_access permissions.
- content_permissions (core): You can grant some permissions based on the CCK field.
- comment_cck: This works as a "ticketing" system. Now I am checking if this integrates with tac_lite and content_access modules.

Tac_lite + Content_access is not a good combination for me because as far as I´ve tested both modules only grant permissions and do not restrict them. So when one of them gives access to one node, it doesn´t matter what happens with the other, the user will have access.

I took a look at the openatrium and it looks good, but I didn´t get very deep so... can´t say anything yet.