I administer our RT installation at work, and it just about meets all of our needs (aside from some minor annoyances). We use it for both support tickets and for bug tracking, and aside from some initial tweaks needed to make it fit the way we work, everything's been running smoothly.
Local customizations were pretty simple once you learn how the overlay system works, and interfacing it with external code isn't too difficult either. We've got a script that scans the incoming ticket queue and associates each one with the appropriate customer account in Salesforce for the sales team (using the Salesforce SOAP API), and an RT query module for mozbot so we can grab basic ticket status via IRC.
I've never used (and until now, never heard of) OTRS, so I don't really have much to say about it. However, I notice that they use Bugzilla for their own tracking, rather than eating their own dogfood.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.