PerlDesk satifies 98% of my requirements, ... I need to show my boss that switching to PerlDesk for Support Tracking only is more benificial than staying with Bugzilla
Here's the problem: PerlDesk satisfied your requirements, but my (good) experience with Bugzilla* leads me to suspect that our requirements may not have substantial overlap. But maybe my requirments aren't your group's requirements.
Start here: Gather up a list of what's required in an issue/bug tracking tool. Get your boss's input on this since s/he's a major stakeholder. Then compare how Bugzilla, your tracker, and other alternative (like RT) satisfy those requirements.
Given the options available, I'm suspicious of the need for new home-brew systems.
* I was using BugZilla mostly as a management tracking tool, to give me oversight on where we stood, so I was leaning most hard on searching and reporting. I've heard good things about RT, too, though I haven't played with it yet.
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.