Brothers, Sisters, and Wierd Things of the 'Cloth';

I have a bit of a problem. My company currently uses Bugzilla for both bug tracking and support tracking. After roughly one hour of using this hybrid thing I got angry and descided to write my own Support Tracker using perl. Now after a couple of weeks, I found out about a great little program called PerlDesk written by J Bennet.

PerlDesk satifies 98% of my requirements, and the database schema is setup easily enough that I could write specific queries as required by my boss.

Here is where all of you come in. I need to show my boss that switching to PerlDesk for Support Tracking only is more benificial than staying with Bugzilla (Bugzilla will continue to be bug tracking database). Would someone please give me some short and sweet ideas of what to point out (regarding Buzilla's Support Tracking abilities?

Please be aware that I will be quoting you

My biggest point is that Bugzilla does not follow standard modules (CGI.pm) and has it's own, there fore I would have to become a Bugzilla specialist to maintain or change the code where needed by my company.

Thank you

Kristofer

Edited: ~Tue Jul 9 18:32:06 2002 (GMT), by footpad:
Moved to Mediations from SOPW, per Consideration.

In reply to Bugzilla vs. PerlDesk - A survey by krisahoch

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.