Slashdot Mirror

← Back to Stories (view on slashdot.org)

Trouble Ticket Systems?

Posted by Cliff on from the tracking-those-bugs dept.

Zen Master Nate asks: "I work for a startup ISP, and part of my job is support. A trouble ticket system would be quite helpful, but all the ones I have found are overpriced and way too complex for our needs. My question is: What trouble ticketing systems do you use, commercial, freeware/open source, or in-house? Also, if I were to write one, what features are needed, which ones are useful, and which are unnecessary? "

1 of 16 comments (clear)

  1. Re:wreq by Hackboy · · Score: 3

    I used wreq at my last job. It was used as a site trouble ticket system and we were planning on replacing it with something more powerful, but I left the company before management decided on a new system. Wreq served the company well for a couple of years

    Strong points:
    • Open source, change it to suit your liking.
    • Easy to integrate into other systems
    • Simple email interface.
    • Fast
    Weak points:
    • Limited "ownership" of tickets
    • No escalation
    • Web interface a little confusing.
    • Searching capabilites limited