Esteemed Monks,

Once again I seek the advice of my knowledgable and generous colleagues here in the monastery.

I run a consulting and contracting practice. Our principal business is the design of electronics which includes miroprocessor and microcontroller coding as well as FPGA and other VHDL design work. As a 'side-line' which is growing rather rapidly I also do some web-app and other Perl based coding.

Until now each engineer or programmer has manitained his own 'bug-tracking' for his jobs. This is no longer working. I need a centralised way of tracking bug reports.

I am aware of Bug-zilla, but I have no idea of the resources required for it. What else should I consider, what advice do any of you have to offer?

jdtoronto

In reply to OT choice for bug reporting systems by jdtoronto

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.