Valerie Bubb Fenwick writes:
> We am looking at things that are missing from bugzilla
> that would hold us back from using this as the sole
> bugtracking tool for Solaris/OpenSolaris, instead of
> the two we are using now.

In addition to Danek's fairly complete comparison (and I agree that
treating RFE as a "severity" is really weird):

  "Can't Live Without"

    We use that "security" flag to bowdlerize bug reports.  Bugzilla
    seems to have no equivalent.

    General access to keywords.  As it stands, you have to have some
    sort of special administrative access in Bugzilla to create
    keywords.  I'm able to create user accounts, products, and flags,
    but I can't touch keywords.  In Bugster, keywords are just plain
    old text strings; anyone can use whatever they want.  (Minor
    downside of the Bugster way: some people misunderstand keywords
    and just stuff the summary in there, larding the database with
    junk.)

    Having cross-references to escalations is extremely handy, so that
    RPE and development don't step on each other.  I have no idea what
    the equivalent would be in Bugzilla, or if there even _should_ be
    one.  (One fix, which would work for Bugster as well, would be to
    demand that RPE engineers working on an escalation set the RE
    field to themselves.)

    The "Version" field can't be edited once set.  Why's that?

  "Nice to Have"

    Justifications, when used properly, are a good thing in Bugster,
    and force people changing priorities to _think_ about why the new
    priority is right and the old one was wrong.  Bugzilla doesn't
    seem to have this.

    The RM field in Bugster is really a "non-NULL technology owner"
    field.  It would be nice to have a field like this in Bugzilla:
    something automatically assigned by the Component selected that
    gives an owner that can be contacted about progress (or lack
    thereof) for a bug, regardless of what "Assignee" is set.  This
    would be sort of like the "QA Contact" field, but would very
    likely have a _real_ email address.

-- 
James Carlson, Solaris Networking              <james.d.carl...@sun.com>
Sun Microsystems / 35 Network Drive        71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677
_______________________________________________
tools-discuss mailing list
tools-discuss@opensolaris.org

Reply via email to