Community HelpDesk, the need for another Ticket System

Events happening in the community are now at Drupal community events on www.drupal.org.
schnizZzla's picture

Hello everybody,

I'm trying to setup a new project:

A HelpDesk is basically a way to communicate problems to the support team or webmaster. It can be a very powerful application that helps organizing user support workflows. Users are capable of tracking their own tickets and moderators and administrators can see the tickets in a organised fashion. They can react to these tickets trough the module and ideally there could come more functionality for different user support work flows as assigning certain issue categories to a moderator of that category.

This project is setup for simple solutions to issue tracking and support of all sorts of websites. Anyone wants to jump into helping this project, I have some difficulties with getting all the access controls working?

I launched a small Demo Page here:
http://helpdesk.berlinerstrassen.com

Regards,

schnizZzla

Comments

Not sure where exactly

fgm@drupal.org's picture

Not sure where exactly you're trying to go: at present your demo looks a lot like just basic nodes and their comments, set up using Views.

I started (and never finished) a full helpdesk/ticketing module when I started drupal 18 months ago (http://www.drupal.org/project/helpdesk ) : you might want to scavenge parts of it, or at least look at the concepts, which may be more interesting than the code itself. A significant part of helpdesk (as opposed to what project module does) is how to charge time, and escalate/de-escalate tickets.

Be sure to check out

merlinofchaos's picture

Be sure to check out casetracker, which has already accomplished a lot of what you're talking about.

Yes, check Case Tracker.

DaveNotik's picture

Yes, check Case Tracker. Some of the things you mentioned are in its plans. I envision a pluggable Time Tracker module, and some work has been started in that area under different names. Any effort you put into things like this is best directed first at Case Tracker, and I for one would certainly welcome additional development.

http://www.drupal.org/project/casetracker

Thanks. :)

--D

http://www.wovenlabs.com

HelpDesk and Private Access Control

BenK's picture

I'm also working on coming up with a HelpDesk solution for Drupal.

Would the Case Tracker module be able to work in conjunction with the Privatespace module (http://drupal.org/project/privatespace) or Private module (http://drupal.org/project/private) to create a node that can be viewed only by the user who originally created the node (as well as "site administrators" who would be our helpdesk staff)?

Some type of "private" access control--so you can't read another user's support requests--would seem to be the key functionality needed for a HelpDesk application.

Thanks for any insights...

I'd suggest posting to the

DaveNotik's picture

I'd suggest posting to the Case Tracker issues area (http://www.drupal.org/project/issues/casetracker) which is were most discussion takes place. Search the issues first and open a new feature request if you can't find a similar issue.

--D

--
http://www.wovenlabs.com

Being back

schnizZzla's picture

I was busy exploring drupal for my needs and I still am. But I think it may be also a better time to post now. After reading your posts and taking some more time in testing.

@fgm
My demo page is basically testing nodes and different levels of access, that's right.
As I always try to use search/google before complaining, I saw your project but being new to drupal I was wondering about the project status of the HEAD version.
I still didn't take a look at your code, but what you describe is basically what I want.
Because drupal was made for communities, I think such functionality should find its way into the drupal core sooner or later. Although it may be a long way still. Aren't you going to support any new version of your project?

@all
I really came to like the Case Tracker module very much, you can expect me posting some issues on this project (soon).
With its cck integration, generic approach and more, it's very useful.
So I startded using Case Tracker to manage the remake of my favourite free music website ;-) with drupal. This way I can manage all cases concerning the remake, further administration and authoring/editing of the site with my buddies. We use the whole CT for this one big project and all CT projects to divide it into different sections/categories.
Apart from CT, Views and Panels I use TAC lite to control different levels of privacy. Using a privacy category with different terms (admin only, all members, editors, moderators, ...) which I can choose to force on different node types and roles. TAC lite makes me able to control the selection/visibility of privacy terms by roles and also individual user rights. That's why you see no cases as guest.
My latest conclusion is that - having already a communication system for the site team - I would "only" need to code some patches (for CT) here and there to integrate a new ticket node type as a simplified case type for CT which will be easier to use for normal members without all the selections cases normally have and fewer categories/projects or even some taxonomy terms to select instead for possible integrate with on help tips etc.

If you are eager to sneak a peek at my CT and you don't care about the german language (UI is still english) tell me, I can make a test account, because the site is semi private as I described above. But there is not that much to see at this point apart from my individual CT configuration, the combination with TAC_lite and more Views e.g. a case filter and so on.

At this point I would like to improve the different views of case tracker either by coding some new features and making some custom css or what would be much better for the community by extending the views integration in CT e.g. I am not able to make a customized "my cases" view (similar to the standard view in CT) because the "assigned to" field is missing in Views and more...

That's it for now, tell me what you think or maybe you have some better ideas and thanks for the feedback this far!

schnizZzla

My left mouse button loves target_blank_linking!
My middle mouse button doesn't care.

BerlinerStrassen.com - Support Your Local Heroes

schnizZzla


BerlinerStrassen.com
- Support Your Local Heroes!

Hi. Helpdesk is a 4.6.x

fgm@drupal.org's picture

Hi. Helpdesk is a 4.6.x module only, that has not even been finished (yet). The code is not very drupalish, because it was my first module attempt, 18 months ago, so it contains lots of unexpected behaviours. Since I do actually need the functionality and none of the existing modules answer that need (issues on any topic, not SD-related, charging time, organizational roles, escalating/deescalating tickets, ...), I'm pretty sure I will someday finish it, maybe for D6.

However, considering the existing project and casetracker modules, i think it would probably be best for most situations to go with either than with the module at this point on time and for still several months, unless you really need the specific functionality it brings and are ready to adapt it for D5.

Followups specific to this module should probably go on http://drupal.org/node/70812 : this thread is best about generic discussion on the need and your module.

Hi! Glad you find Case

DaveNotik's picture

Hi!

Glad you find Case Tracker to work for you. Any and all contributions are certainly welcome, and the current maintainer (Morbus Iff) is doing a great job of staying on top of it all.

@fgm: It'd be great to see your efforts applied to Case Tracker and related development, especially because it has good momentum. I imagine a Time Tracker module that integrates well.

--D

--
http://www.wovenlabs.com

@fgm "I'm pretty sure I will

schnizZzla's picture

@fgm
"I'm pretty sure I will someday finish it, maybe for D6."
Ah, that's what I wanted to hear ;-) I actually thought that maybe won't come up with any newer versions...

Generally, it's good to to hear that there are enough people around here, who are interested in such functionality in the long term. This is definetely not a small project, but will be a big benefit for the community.

What's very important - apart from how tickets are treated by the site staff internally and important functionality that fgm mentioned (escalations, time, roles, ...) - that tickets are designed for the user that generates them, so if they aren't easy to use they are pretty useless. Usability should be a main aspect of a help desk.

schnizZzla
You can't prove it won't happen!

Support Your Local Heroes

schnizZzla


BerlinerStrassen.com
- Support Your Local Heroes!

Issue tracking and software releases

Group organizers

Group notifications

This group offers an RSS feed. Or subscribe to these personalized, sitewide feeds:

Hot content this week