Very nice to have / painful to live without

  - While at the current level, interest lists are a "nice to have", if
    we're going to move to bugzilla for everything, we really do need a
    more scalable solution.  Having to go in and create a watcher alias for
    every single component is tedious.

  - When selecting components within a product, there's no immediately
    available description for each one -- you have to click on the link,
    and you might not see it or think to do so.  This ends up meaning that
    we triage a lot of bugs from Distribution / opensolaris / packaging to
    Development / pkg / *.  Some of the problem exists because there's only
    a single product under Distribution, so bugzilla jumps directly to it,
    rather than forcing the user to pass through a "choose a product" page
    that would have some descriptive text allowing us to explain why you
    might not want to be here to file packaging bugs.

  - There's no way to edit comments.  This means that you have to be
    incredibly careful to get everything right the first time, since any
    updates you might want to make may get lost in the noise of future
    comments.

  - Graphs and charts have to be set up by an administrator, and they can't
    be run on historical data.

  - An individual bug can only have one Hardware / OS / Version associated
    with it, unlike Bugster, which can have multiple service records.

  - You can't add an attachment and make other changes to a bug in the same
    transaction (other than adding a comment).

  - There's no "see also" undirected connection between bugs.  There's
    blocks / depends on, which is nice, but sometimes it's good to just
    have bugs related to each other, so you can get a sense of what else
    you might want to look at, without trawling through the comments
    looking for links to other bugs (which might not even be links if
    people don't know about the "bug #?[0-9]+" convention.

Nice to have

  - Programmatic bug modification.  There may be an interface for this, but
    I haven't found one.  Admittedly, I haven't looked all that hard.

  - Saved custom searches are great, but it'd also be nice to have saved
    custom bug templates, for those of us who file a lot of bugs.  I
    believe there's similar functionality in the bugster GUI.  Bookmarkable
    templates aren't the same -- I want links down at the bottom of my
    page.

  - Related to editing comments above, when bug A gets marked as a
    duplicate of bug B, a comment to that effect is added to each bug's
    comment log.  If that turns out to have been incorrect, and the
    duplication is removed, the comments stay.  I'm not sure whether that
    makes a difference in the "Most Frequently Reported Bugs" page
    (duplicates.cgi).

  - There's no distinction between different types of comments -- are they
    just comments, are they evaluations, etc.  I'm finding, over time, that
    I care less about this than I did.  I think I'd still like the ability
    to mark a comment as an evaluation, but I do actually like the
    chronological order of the comments, rather than per-category.

  - The Summary field seems to have arbitrary length (or close enough).
    The 100 character limit in Bugster is nice, in that it limits people
    from going on and on in the summary.

  - The hack of using the QA contact as a place to stick a watcher alias
    has the side effect that when moving bugs from one component to
    another, the new alias isn't automatically moved to the new component's
    QA.  By now, many of us know that we have to reset the Assignee and QA
    contact when moving bugs, but not everyone does, and so sometimes bugs
    will get moved, but missed.

Other Differences

  - RFEs are just a distinct Severity of bug.  I'm not sure whether that's
    bad or not, though it can be pretty weird.

  - There's no concept of "initial evaluator", as distinct from the aliases
    that get a copy of every single bug mail.

  - Email shows only the changes made, rather than displaying the entire
    bug.  That could be construed as good or bad, though when a bug is
    moved from one component to another, it can be a bit annoying not to
    have the bug history immediately in your inbox.

I'm sure there are other things, but this is what came off the top of my
head and a bit of poking at the interface as a reminder.

Danek
_______________________________________________
tools-discuss mailing list
tools-discuss@opensolaris.org

Reply via email to