Support. Casetracker. Storm. Project. Trouble Ticketing System. Comment CCK.
Hooray for opensource, and the ability for many people to spend a lot of effort trying to achieve the same end!
And yes, I know each one'd say 'no ours is slightly different'. I would certainly hope so, or else how did these projects get approved on d.o? I thought it was all about reducing duplication of effort.
So, what ticketing/issue tracking system have you implemented on Drupal, and what made you stick with your choice? I've tried almost all of the above. For me, Support is working great on my feature server. It supports mail notifications straight off the bat, has a sensible UI. Strange choice of CSS colours for ticket states (green for 'active' ?).
Casetracker looks ok. I see there's 'dependency' support now, at least in Atrium. But why can I close a ticket that is dependent on a ticket that is still active?
Anyone implementing a setup whereby e-mail sent to an imap/pop folder is converted into a ticket? I see Support, erm, supports it.
Which of these modules should I choose to hack away at until it works like RT, except without the Perl insanity, and that ghastly giant 'attachments' table that stores images and whatnot in the database? Can I get the awesomeness of Jira without being rodgered by Java in the process?
What do you use, whether it be any of the above or a custom solution, and why?
to_do and todo are also out
to_do and todo are also out there. I use to_do for personal use.
The return argument
Playing devils advocate:
Which two modules would you merge, and why?
I think that the debate gets a whole lot harder when that question is introduced - especially the 'why' part. The article seems gloss over that part!
I don't know if I'd want to
I don't know if I'd want to merge any collection of modules that fail to do the job by themselves or combined :) they all miss desperately needed features such as:
- Parent > Child dependencies in tickets (I almost got that working with Casetracker and nodereference but it was a major hack)
- Time tracking on a ticket: marking how much work has been done on the ticket, tallying it up
- Reporting
Unfortunately these other horrible applications like RT and bloaty Jira still do it better. It's another one of those awful realisations that 'Drupal isn't meant for everything' :)
Post new comment