Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 


Forgot your password?
Close
typodupeerror
×
Businesses IT

Ticket Tracking and Customer Management? 236

Posted by kdawson from the looking-for-a-package dept.
An anonymous reader writes "Like many Slashdot readers, I'm sure, I run a small side business doing IT consulting in addition to my day job. I'm looking for a good open-source ticket tracking system that I can run under Linux, preferably one that also has some customer management features. I'd like to be able to maintain a separate record for each job, along with time tracking, work logs, and information about the customer. Much of what I see on Sourceforge is, as usual, pre-pre-pre-alpha with no actual code. Does anyone have any suggestions for a project that might fit my needs?"
This discussion has been archived. No new comments can be posted.

Ticket Tracking and Customer Management? More

Ticket Tracking and Customer Management?

Comments Filter:

  • JIRA... (Score:3, Informative)

    by Forbman ( 794277 ) on Sunday July 29, 2007 @09:58PM (#20037295)
    at least, that's what Merrill Lynch uses.
    • but it does look pretty good.

    • Re:JIRA... (Score:4, Informative)

      by flowsnake ( 1051494 ) on Sunday July 29, 2007 @10:04PM (#20037351)
      JIRA is nice, but I'm not sure it satisfies the poster's open source requirements. AFAIK, the source code is only available to 'commercial users' http://www.atlassian.com/software/jira/docs/v2.6.1 /building.html [atlassian.com] which I assume requires a paid-for commercial licence http://www.atlassian.com/software/jira/pricing.jsp [atlassian.com]. I guess it depends on one's definition of 'open source' as to whether this is sufficiently open.

    • Re: (Score:3, Informative)

      by Artega VH ( 739847 )
      JIRA isn't open source although it is quite nice and I use it internally at my workplace.

      I might suggest Trac [edgewall.org]. It's an open source ticket management system integrated with Subversion. Probably doesn't have the extensive customer management features but with the wiki+ticketing is done quite well and can no doubt be used to satisfy the posters needs.

    • Re:JIRA... (Score:5, Informative)

      by arivanov ( 12034 ) on Monday July 30, 2007 @02:14AM (#20039137) Homepage
      This is more for internal issue tracking and software development issue tracking. At least this is the way I have seen it used.

      If you want to use something for external facing issue tracking and make it customer facing straight away I would suggest RT by Best Practical. It is GPL and relatively open as far as brain effort to extend it is concerned. It is also trivial to use for issue oriented CRM/sales which is typical of a service company or consultancy.

      It is used as the primary system for tracking customer facing issues by companies with turnover in the billions like NTT/Verio. It is also used by small non-IT companies like my favourite plumbing supply shop http://www.plumbworld.co.uk/ [plumbworld.co.uk]. It is also often adapted to integrate the support, CRM and sales process like in Claranet http://www.claranet.co.uk/ [claranet.co.uk]. Judging by the people on its mailing list it is also running in pilots and internal projects at Audi, BT and a couple of other places.

      It has been in stable for nearly 4-5 years now. I have used in my previous job, and while it is not completely free of bugs, it is possibly the best general purpose issue tracking system I have seen so far.
    • http://www.project-open.com/ [project-open.com]

      It's an all in one ticket tracker, CRM, timesheet, project management (including GanttCharts), WIKI, form, full-text-search, etc. and it includes financial management. So you can create invoices directly from the time you spent on tickets and projects.

      The downside: It uses TCL and AOLServer instead of PHP and Apache.
      • I did an extensive search just a few months ago (while extensive means it probably is not as intensive as it could be). About ]Project Open[ I saw two "flaws":
        1) Out of documentation, it seemed that the request tracking module was still not developed; since by the time I was specifically looking for issue trackers, that meant the end for it.
        2) It's based out of AolServer. I want Open Source because I can, well, open the source and tweak it; since I'm not an AOLServer/Tcl "fan" it went even lower on my lis

  • RT (Score:3, Informative)

    by oskard ( 715652 ) on Sunday July 29, 2007 @10:01PM (#20037327)
    Been using RT [bestpractical.com] as a ticket tracker at a few places I've worked at. Works well.

    • Agreed on RT as First Step (Score:5, Informative)

      by zamboni1138 ( 308944 ) on Sunday July 29, 2007 @10:10PM (#20037387)
      This question has come up [slashdot.org] before [slashdot.org], and I usually answer the same way. RT: Request Tracker [bestpractical.com] is a good place to start. It is a Perl+Apache+MySQL based open source solution. The first few times you install it can be tricky. Find a good and current how-to.

      I have since moved away from RT and now use an in-house designed system. But I still give it two thumbs up.
      • One small caveat that I see with all the products mentioned is they all seem to be tailored towards / around software development / ticket / bug tracking. Can anyone suggest software more suited to a workshop? Say allowing tracking of jobs as they arrive/ leave etc? None of the options people list seem to cater or are adaptable for this purpose.
        • How do you mean tracking jobs as they arrive / leave? Barcode scanned objects on arrival or similar?
          We've adapted various business practices to take advantage of RTs strengths, and pretty much most of our company uses RT to one extent or another, from IT through to sales. We've set up autoforwarders on our mail servers so that e-faxes to certain numbers arrive in particular queues, we've got cron jobs setup to send e-mails out for regular departmental tasks and so on.
          • How to explain. I guess the best way is to describe the 'story'

            My computer store has a workshop. We have computers / printers / anything at all come in to be 'fixed'
            I would like to be able to enter the 'job' as the customer brings in the computer / whatever, enter the customers contact details, description of the fault(s) etc. (issue tracking?)
            Whilst working on the fix, i would like to be able to add 'notes' to the 'job' I would also like to be able to track phone calls (CRM?)
            If the job was virus removal /
            • RT Does all that.
              And more.
              (Together with its "cousin" RTFM)

              Advice: Install FreeBSD 6.2, update the ports and install it via the ports-system.

              Installing and using RT is one of the most sensible things you can do in IT.
            • I already said it but, now, looking at your more detailed use-case, I reaffirm: OTRS is probably what you are looking for.

    • Re: (Score:1)

      by Anonymous Coward
      MIT over here uses RT to manage all IT-related tasks too. It seems to work well.

      • Re: (Score:2, Funny)

        by therufus ( 677843 )
        With all those acronyms, that could have possibly been the geekiest sentence ever! ;)

        It's humor people, laugh...

    • RT For sure (Score:3, Informative)

      by g8orade ( 22512 )
      Definitely thumbs up for RT.

      We are on a mission at the company where I work to replace all email / attachment based work management with it.

      You'd be amazed how far you can push RS using the concepts of owner, status, subject line, journaling, parent child / depends on depended on by tickets, auto-notification, attachments etc. all built in.
      If you think you need more structured data, you should at least see how far you can get prototyping it first in RT, using its minimal custom fields but also its custom v

      • Re:RT For sure (Score:4, Interesting)

        by yarbel ( 1134645 ) on Sunday July 29, 2007 @10:21PM (#20037483)
        RT does not scale well at all however. We have had to make major modifications to the source in order to support 200,000+ tickets.

        • Did you index it? (Score:3, Interesting)

          by g8orade ( 22512 )
          hmmm.
          We've been running it for 2 plus years now, have 100,000 plus tickets, and it's quite fast. We did have to add an index recently when coming back to All Tickets view and many of us have a lot of queues.

          I see others have had issues / bad experiences. Our shop has some very experienced Oracle guys and someone who, so far, has been able to make it do everything we've wanted it to using Perl mods. (auto assignment based on subject contents, custom fields, etc.).
          Maybe other tools are easier when you don't h

          • Re: (Score:2)

            by notque ( 636838 )
            I think the support is important. I was able to hack together any sort of odd request that the business asked. That was something I couldn't have done with other systems. You got whatever they put in with other ticketing systems. With RT, you ask for something, you get it provided you have some support.

            We connected into other systems, had real time displays of information to help them answer questions inside the system. It was very nice until we were bought out, and started using a monolithic system that ha

        • Re:RT For sure (Score:5, Informative)

          by jesse ( 306 ) on Monday July 30, 2007 @12:14AM (#20038293) Homepage
          yarbel,

          I'd love to hear a bit more about the scaling problems you had over on rt-devel@lists.bestpractical.com. We have end users (some of them paying customers, but plenty of them not) with well over a million tickets in their RT instances without any sort of performance problem.

          And I'd certainly love to see patches for anything you had to do to get performance up to snuff. (Since, well, we'd certainly like to improve things if users are running into trouble.

          Best,
          Jesse (RT's chief catherder)

          • Re: (Score:2)

            by kobaz ( 107760 )
            I had some scaling issues about 2 years ago. I can't go into much detail since I no longer have the install. We had about 10,000 tickets on a dual 1ghz machine with 4 gigs of ram. The server wasn't used for much else other than some small, low traffic websites. Loading the all tickets screen would take a good 40-50 seconds. Loading the queues (I forgot what they are called... the per person assignments) took about the same time as well. Our guys (3 users) were getting really slowed down waiting almost
            • I saw this issue as well. A least part of this slow down was caused by RT not house cleaning its sessions. This resulted in RT querying a current session with all sessions that were ever created. I'm not sure if that is still a problem.

    • Re:RT (Score:5, Interesting)

      by zeath ( 624023 ) on Sunday July 29, 2007 @10:24PM (#20037509) Homepage
      When researching a ticket tracking system to implement at my workplace I came with no experience in any non-proprietary system. I compared RT and trac [edgewall.org] side-by-side and found trac to be much more readable and user-friendly. Even for me, when setting it up, I spent an entire day trying to make heads or tails of the RT interface, while in a day I already had trac up and running and I was showing others how to log in and use it. Now that it is in production, what surprises me the most is the ease with which the non-IT department managers use it for tracking their tickets and project progress.

      The irony of the situation is that I do specialize in Perl, which is why I went toward RT first. I assumed it would have been the better choice for making any changes to the underlying system, but in the process of working with trac I've learned Python enough to hack together a number of custom solutions for our needs.

      Since I didn't go any further with RT after that first day, I can't say how well that would have worked, but in my case RT did leave a bad taste in my mouth.

      • Re:RT (Score:5, Informative)

        by notque ( 636838 ) on Sunday July 29, 2007 @11:15PM (#20037851) Homepage Journal
        RT used to be much more difficult to install than it is now. Even then, it wasn't very difficult if you are a Linux Administrator with a knowledge of perl.

        Now, it's extraordinarily simple. Initial understanding of some of the rights management will take a little bit of time depending on how complex you want it to be.

        • Re: (Score:2)

          by zeath ( 624023 )
          My time frame for comparing the two packages, which I did not mention, was about a month ago. It wasn't that it was difficult to install; it was the configuration after it was installed that felt like I was on a treadmill, I was spending all my time working backwards and fighting with features I didn't need and managing permission settings way beyond the complexity that I required. In trac I was customizing ticket fields and setting up project workflows in a fraction of the time that it had taken me to give

        • Re: (Score:2)

          by jp10558 ( 748604 )
          Let me just say that I can't speak to the install as it's been up and running since before I started working at my current position. However, the user interface is abysmal. I think there might be one person who knows how to use the web interface. The web interface is PAINFULLY slow. Everyone uses our e-mail gateway. I can search my 7,000 + past e-mail history in Thunderbird / IMAP much faster and simpler than using RT's interface.

          I can't think of a web interface I've seen that's as bad. Using RT's web inter

      • Re: (Score:2, Informative)

        by tirerim ( 1108567 )
        RT is indeed extremely customizable, and with enough effort can be made to do just about anything (we have scripts that automatically update tickets based on the state of files in our CVS tree, for example). However, there are a lot of settings, and the documentation is extremely haphazard, so if you want to do something complex, and you don't happen to think like an RT developer, it can take a long time to figure out how.

        And as for making really low level changes, the source can only be described as labyr

    • Re: (Score:2, Informative)

      by mrmagos ( 783752 )
      Oh, if I only had Mod points. RT is great. Once you get used to it, it's not too difficult to customize, and can be extended with the user-contributed modules (e.g. LDAP/Active Directory integration). There's even an O'Reilly book [oreilly.com] that outlines customization for different requirements/environments.

    • Re: (Score:2)

      by cblack ( 4342 )
      Another thumbs up for RT. I have used a few others including custom systems in the past and RT is towards the better end of the systems I've used. (trac is also nice). One of the really great things about RT is how easy it is to integrate email into the workflow. It is very easy to have an incoming email address like "helpdesk@mydomain.com" where people can send requests and get a link to their ticket. In addition all email you send in reply to that mail (or any that have the ticket number in the subject) a

    • Re:RT (Score:5, Funny)

      by More_Cowbell ( 957742 ) on Sunday July 29, 2007 @10:36PM (#20037609) Journal
      The website is down (slashdotted?) Do you know where I can submit a ticket?

    • Re: (Score:2)

      by notque ( 636838 )
      Another vote for Request Tracker, the best ticket tracker I've ever used, deployed, and customized.

    • Re:RT -- Use RoundUp instead.. (Score:5, Informative)

      by cowmix ( 10566 ) <mmarch.gmail@com> on Sunday July 29, 2007 @11:11PM (#20037827) Homepage
      RoundUp (which is Python based) is a great system..

      Its self contained.. a GREAT email interface.. easy to setup and easy to extend.

    • Can't agree. It's a pig to install, requiring dozens of Perl modules that stomp all over the filesystem and in FastCGI configuration at least it crashes regularly. It's also, as others have pointed out, more of a bug tracker rather than a support call tracker. If you need something akin to a bug tracker, then go with Bugzilla - it's also written in Perl, but it has fewer dependencies.

  • I'm looking for the same thing, only I need it to run under windows.

    I'm looking for something web-based, allowing clients to enter tickets, and programmers to respond to them.

    Any ideas?
    • I'm sure glad there is some Woodland pride to compete with all this Davis pride just South. Nice website.
    • Try PHProjekt [phprojekt.com] - I use it, and am quite happy with it. Group policies, project/task tracking, time logging, threaded discussions, etc. Pretty full-featured, simple to use, I can grant and limit access to whomever I choose.

    • Re: (Score:3, Insightful)

      by crossmr ( 957846 )
      if its web based..no you don't need it to run under windows. Its why god invented virtual machines. Web based means the back end should be completely transparent to the users and it doesn't matter if its run on a gerbil strapped to a hamster chasing a toaster.

      • it doesn't matter if its run on a gerbil strapped to a hamster chasing a toaster.

        I'd be careful of gerbil/hamster based backends. There's always that one sysadmin whose just too interested...

      • Other than ping delays and latency while the hamster sleeps. Though, I suppose it would still work...
    • We ran MantisBT [mantisbt.org] on a Windows 2003 server at my previous job. Added 30 or so extra lines to the config file which took the user's NT logon (automatically authenticated with WIA in IIS), looked them up in the user table, if they weren't present, did an LDAP call to find out who they are and add them to the database automatically, and finally set up the session to make them logged in. It made it seamless (though new users would have to visit the site once to get their account created in order to be added to
      • We ran Mantis at a previous place and liked it. Akin to Bugzilla but with a nicer interface out of the box, as I recall.

    • I'm looking for the same thing, only I need it to run under windows.


      You can have features, windows, and running. Choose two.

  • Eventum (Score:5, Interesting)

    by Lordrashmi ( 167121 ) on Sunday July 29, 2007 @10:02PM (#20037339)
    A bit of shameless self promotion (since I am the lead developer), check out Eventum [mysql.org].

    It might not be the perfect fit for you, but it is stable and customizable. Right now it is lacking built in customer management features, instead it relies on a Customer API to integrate with other systems. Right now I am working on integration with Sugar CRM but do not yet have an ETA on when it will be released.

    • Re: (Score:3, Informative)

      by jumperboy ( 1054800 )

      I'm currently evaluating Eventum for both IT support and generic issue tracking for service departments with no IT component. The only thing that feels beta about it is its obvious origin as a software issue tracker, but it won't require much modification to support generic issue tracking. Other than that, it is very stable, and customizable in a good way, not an evil, "I can't use this unless I completely rewrite the source code" kind of way.

      I have experience with RT, and have installed it for clients w

  • Does citrusdb (http://www.citrusdb.org/) do what you need?

  • One (Score:5, Funny)

    by m0nkyman ( 7101 ) on Sunday July 29, 2007 @10:09PM (#20037379) Homepage Journal
    Postgresql. You may need to do some minor work customizing it....
  • It's not Free, but you might want to check out Cerberus Helpdesk [cerberusweb.com]. They've got a free (beer) version [cerberusweb.com] that's subject to some limitations. We considered using it at my last job (before settling on another solution.)
    • What did you end up settling on?
      • We ended up settling on a ticket tracking system by Intuit. I was pushing for the Cerberus solution, but the higher-ups settled on that, for whatever reason.
    • I can vouch for Cerberus, it's a great product. Yes, there's a free version, but the full license is about $300, which is peanuts for a ticketing/crm system, and it is the best one I've used.

      I've worked for companies that spent ludicrous amounts of money on ticketing systems, and I've always wished I could go back to Cerberus. I just left a job that used RT, and I hated it.

  • trac (Score:5, Informative)

    by zeath ( 624023 ) on Sunday July 29, 2007 @10:10PM (#20037395) Homepage
    I implemented trac [edgewall.org] at my workplace as a change control and task management system. We use it for both internal projects as well as billable work, with a number of custom fields for supporting our quoting system and quality control. The built-in Wiki also doubles as our IT documentation repository, all in one easy to access location.

    It is extremely extensible, and anything not readily available [trac-hacks.org] can be easily created. It didn't take much time to learn the class and data structures and I've modified existing plugins and written a few of my own to support our needs.

    • Re: (Score:1, Informative)

      by Anonymous Coward
      Trac is a nice tool. Easy to setup easy to use. It can be used with
      Postgresql. You can authenticate with htdigest. There is also a
      command line interface so you can automate administration with scripts.
      You can also install subversion and browse the source trees through Trac.

    • Re: (Score:2)

      by doti ( 966971 )
      One more vote for Trac.

      IMO, it's main strength is the simplicity for the user. An issue tracker is no good if nobody will use. I saw it many times: the IT department decides for a tool, install it, teaches everybody how to use it, and how important it is, but in the end nobody uses the tool. Trac interface is simple and nice, it does just what it has to do. Trac does not get in your way and feel like a burden.

  • We use JIRA (Score:5, Informative)

    by GoatRavisher ( 779902 ) on Sunday July 29, 2007 @10:14PM (#20037429)
    JIRA runs under Linux. It is not open source, but the cost of the application and support is well worth it. I believe it is free to use for open source projects. They also provide the full source code, which has allowed us to heavily customize the application. When I started evaluating issue tracking systems this page proved to be rather useful http://en.wikipedia.org/wiki/Comparison_of_ticket- tracking_systems [wikipedia.org].
  • Write one. If it's good, sell it.
    • Write one, and if its good add it to the marketplace filled with hundreds of existing ones. Sometimes it is better to use someone else's hard work.
  • While not conceived as a ticket tracking app, phpBMS might be able to suit your business better than a plain old ticket tracker. phpBMS runs on LAMP and can manage customers, invoicing, and sales/prospecting. I found it while looking for a way to do billing but it's turned out to be good for managing contacts.

  • Vtiger (Score:5, Informative)

    by Blackknight ( 25168 ) on Sunday July 29, 2007 @10:29PM (#20037547) Homepage
    Check out Vtiger [vtiger.com], it's a really nice CRM and also has ticketing features.

    • Re: (Score:2, Informative)

      by yhetti ( 57297 )
      Seconded. Vtiger is an excellent system that's based on a fork of SugarCRM from a while back. I've been running it for about 8 months production and I've been extremely happy with it. You can make custom fields for time tracking and cheat a little bit to get asset management. Overall, B+/A-

  • We're using kayako ( http://www.kayako.com/ [kayako.com]) as our user facing trouble ticketing system. It's not free (cost us something like a couple of hundred US$) but it is very functional and includes mechanisms to track costs. It has a bunch of stuff included that we don't use - like live support etc - as well as a bunch of cool stuff that I haven't seen elsewhere (like AJAX based searching of knowledge base articles as someone updates a trouble ticket). It also integrates nicely with our LDAP based single signon
  • Some people have been able to run Remedy via WINE under Linux.

    http://appdb.winehq.org/appview.php?iVersionId=232 1 [winehq.org]
    • Huh? Remedy is an expensive commercial system. Why would he want that? (much less under WINE).
  • Trac [edgewall.org] is an enhanced wiki and issue tracking system for software development projects. Trac uses a minimalistic approach to web-based software project management. Our mission is to help developers write great software while staying out of the way. Trac should impose as little as possible on a team's established development process and policies.

    It provides an interface to Subversion, an integrated Wiki and convenient reporting facilities.

  • OSTicket (Score:2, Interesting)

    by appleguru ( 1030562 )
    http://www.osticket.com/ [osticket.com]

    It works well; I use it integrated with Help Center Live [helpcenterlive.com]

  • Keystone is still alive and kicking. (Score:3, Informative)

    by Shayde ( 189538 ) on Sunday July 29, 2007 @10:53PM (#20037697) Homepage
    Take a look at http://www.stonekeep.com/keystone.php [stonekeep.com]

    Opensource, non-alpha, many many users active, still being supported and worked on.

    (Obdisclaimer. I wrote it. :)
    • How about putting your demo back online so we can test / see the product!

      • Re: (Score:2)

        by Shayde ( 189538 )
        The demo is offline because folks were spamming it. The product page has screenshots on it though.

        Drop me emailif you want to see the live demo.

  • COULD NOT FIND ANYTHING ?? (Score:3, Informative)

    by kevorkian ( 142533 ) on Sunday July 29, 2007 @11:00PM (#20037765)
    wow .. all he found was "pre pre pre alpha alpha alpha"

    the author did not do a very hard search.

    First and for most .. RT Open source , even has commercial support if you want.Ive been using RT in many forms for at least 10 years now. I remember it back in the late 90s.

    And then of course there is JIRA. This may be more for dev work. Most places ive been used RT for anything that MIGHT face the customer and the areas that had 'issues' and 'projects' that would end up closing at some time. But JIRA was used by the devs for bug tracking and coding projects.

    of course there are a lot of others .. remedy is another that pops into my mind.

    Seriously though. How could you have enough experience and knowledge to run your 'side business' and never have run into either of these projects in your travels. Where have you really worked that they have not used a ticketing system ? Or perhaps you are fresh out of school. But even fresh out of school. I would think that even the dorm network operators would have used SOME sort of ticketing system that you would have been exposed to , if even from the 'customer' side.

    If your google-fu is so weak as to have not found these , then I fear for your customers.

    there is even a nice wiki page comparing all the products..

    http://en.wikipedia.org/wiki/Comparison_of_issue_t racking_systems [wikipedia.org]

  • This has been covered in a few previous "ask slashdots". When I was looking for a ticket system last time, I found some references to OTRS and ended up implementing at my company. IT supports ~200 people and we use it to track helpdesk, report, and feature requests. The system is open source and runs on a number of platforms including Linux and Windows.

    • Re: (Score:2)

      by ShaunC ( 203807 ) *
      Add another vote for OTRS. It's what we use at work to manage all sorts of incoming helpdesk tickets, feature requests, bug reports, etc. It doesn't have any sort of calendaring/timetracking feature that I'm aware of, but it supports internal-only notes to be attached to any ticket. You could easily use this capability to keep track of the time you spend working on a particular issue.

  • Major missing point... (Score:3, Insightful)

    by Sparr0 ( 451780 ) <sparr0@gmail.com> on Sunday July 29, 2007 @11:33PM (#20037951) Homepage Journal
    All the other replies are pointing out great "ticket tracking" software, but I think that is the easy half of this request. I too have searched for what the original submitter is searching for. The key thing that is missing from the existing offerings is hour and work logs. Put simply, at the end of a ticket we need how much to bill the client for. Integrated invoicing would be awesome.
  • I think dotProject will do most, if not all, of what you need....from the site:

    Features Include:
    • User Management
    • Email based trouble Ticket System, (Integrated voxel.net's ticketsmith)
    • Client/Company Management
    • Project listings
    • Hierarchical Task List
    • File Repository
    • Contact List
    • Calendar
    • Discussion Forum
    • Resource Based Permissions

  • You say you want a ticketing system, but that doesn't sound like what you really need (if it were, I'd suggest RT for issue tracking or Trac for defect tracking).

    I'd take a look at SugarCRM [sugarcrm.com], or one of it's forks instead. MySQL only, so be careful to keep regular backups.

  • I have used Mantis [mantisbt.org] in my former job for that kind of stuff. As far as I remember it does all you want.
  • What I like about vTiger is that it allows you to try it all - SugarCRM, Zimbra et all all want money upfront before you can test the useful bits..

    Website is vtiger.com.

  • I've been using Trac [edgewall.org] for a couple of years now, also for external projects where customers directly submit tickets. It was a bit rough around the edges, but over the last year a number of good improvements have gone in without compromising the ease-of-use.

    This is a ticketing system where people don't need an hour of training to understand what's going on. The integrated wiki allows for note-keeping (I tend to use it for tracking my hours too), and the SVN-browser is simple but useful.

    If you need something
  • I work for a company that chose Sugar CRM [sugarcrm.com]. We wanted something where we could connect it to our own customer database, and could add links to our own tools, like extra buttons to edit the customer info, purge them, perform system maintenance, etc. Unfortunately, none of the systems we found allowed this. The best we could do was to find an open source system that was easy to edit. We modified the pages to include extra buttons that link to external web applications. It's not the best integration, but it
  • GLPI http://www.glpi-project.org/?lang=en [glpi-project.org] is worth a look.

    It's LAMP-based and does inventory tracking too. It supports user-submitted tickets and has a rudimentary concept of service levels/escalation. Reporting needs some work, but you can always use third party tools for this.

  • We tried Trac at work for a ticketing system, and it was ludicrously hard to install. The upshot was neither I, nor the other sysadmin, could get it going acceptably. Mantis was an easy install (except for having to tell MySQL to use pre-4.1 (?) passwords), and Mantis is what we've continued to use.

        mark

  • doyourownwork = asshole (Score:5, Insightful)

    by dbc001 ( 541033 ) on Monday July 30, 2007 @09:21AM (#20041587)
    Whoever tagged this post as "doyourownwork" is an asshole who has no understanding of the way The Internet and it's online communities work. For any question that gets posted on Slashdot, there are dozens if not hundreds of Slashdot readers who want to know the answer. I wouldn't be surprised if 20% of the Slashdot community is running some kind of business that might have a need for a ticket tracking and CRM software setup. Many Slashdot readers are also very friendly, so while a person could easily spend hours researching a question like this, it's far more effective to come to Slashdot and benefit from the experience of it's users.

    So to all the douchebags who criticize people who ask questions on Slashdot: FUCK YOU.
  • Comment removed based on user account deletion
  • This isn't a bad package it works under linux and allows you to have different levels of users. Your customers are able to look up their tickets to watch the progress of resolution. (If you allow it)

    http://www.phpsupporttickets.com/ [phpsupporttickets.com]
  • Try out Basecamp [basecamphq.com]. It's pretty straightforward, and it's more than a cheap wrapper around a database. The views are well thought out, just the right amount of AJAX to make your day go easier, and good collaboration support. Start off free and pay if you need more than the free account provides. It doesn't get very expensive. If that's not your thing, put down another recommendation for trac.

  • Mojo Helpdesk (Score:3, Informative)

    by Chaswell ( 222452 ) on Monday July 30, 2007 @10:18AM (#20042331)
    I read through a lot of the comments and saw so many mentions of enterprise level ticket tracking and development management. You actually asked for a ticket tracking for IT sidework. I use Mojo Helpdesk [mojohelpdesk.com]. They have a free plan, 30 day free trial for their pay plans and gives you a central location to track open issues and receive reedback from clients.

    Hope this helps.
  • I have had success with DCL.

    http://sourceforge.net/projects/dcl/ [sourceforge.net]

    It's been so long since we set it up, I frankly don't remember the details... but it has been running for years now without incident.

    enjoy!

    .

  • That's what I use, and it's worked great for me for 5 years running.

    http://www.centriccrm.com [centriccrm.com]
  • We've been using OTRS http://otrs.org/ [otrs.org] for quite a few years and love it. It just plain works. It can use LDAP for a customer DB which can be also used with SugarCRM if a CRM is needed. We also use the LDAP directory to control the Java Messaging system for mail. We have had no down time in 4 years using this system. Its written in Perl and uses MYSQL for a DB. Yes it runs on Linux!
  • When I was searching for yet another request tracker a while back, I came across:

    http://en.wikipedia.org/wiki/Comparison_of_issue_t racking_systems [wikipedia.org]

    Personally, over the years, I've used Bugzilla, RT and Mantis and they are all very good. Bugzilla is hard for non-techies to understand. Mantis may be a little feature poor and is good for simple bug tracking. RT seems to be the best for general use by techies and muggles alike.

Slashdot Top Deals

E = MC ** 2 +- 3db

Close