On Mon, 2 Mar 2009 17:12:16 -0800 Danek Duvall <danek.duv...@sun.com>
wrote:
> - When selecting components within a product, there's no immediately
> available description for each one
When you're filing a bug, there is, unless you've customized it
out or aren't on a new-enough 3.2 release to have it.
> - Programmatic bug modification. There may be an interface for
> this, but I haven't found one. Admittedly, I haven't looked all that
> hard.
The XML-RPC API is the entire programmatic API. It will improve
in future versions.
> - 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).
The page works off the actual duplicates, not on comments.
> - 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.
It has a 255-character limit.
> - 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.
Oh wow, your guys's Bugzilla is so old that it's still using
the old UI. You really should update to a stable version where you will
see that this is not a problem any longer.
-Max
--
http://www.everythingsolved.com/
Competent, Friendly Bugzilla and Perl Services. Everything Else, too.
_______________________________________________
tools-discuss mailing list
tools-discuss@opensolaris.org
