On 11/2/07, Dan Price <[EMAIL PROTECTED]> wrote: > I've been using the bugzilla instance for several days, and have past > experience with the mozilla.org bugzilla.
> Here is some unsolicited feedback.... I'm always trying to solicit feedback :) [I'm timeless on #opensolaris], so is the whole Bugzilla team. Enhancement requests can always be sent to the Bugzilla project directly, https://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla or you can talk to awake developers (and some idlers) on irc.mozilla.org #mozwebtools I'm going to skip points which rich has already covered... > A couple of questions: > - Can I effect the columns in the list view? One thing > that Monaco, our internal tool has, which I like, is > "Age" in its default output. This is humanized, and > is therefore a nice narrow column. > > 1 week = 1W, 3 months = 3M, 2 years = 2Y In a system where a bug follows this path: filed 1/1/2006 assigned 2/1/2006 patched 3/1/2006 released 4/1/2006 resolved 5/1/2006 reopened 6/1/2006 (rejected) viewed 7/1/2006. What's the age? 1M or 6M? And no, it doesn't look like we have an Age option in colchange, however, before I'm willing to write such a feature, I need people to define how it should work. The problem we have in mozilla.org and many other places is that Age ends up with a number of incompatible definitions most of which are absolutely useless. https://bugzilla.mozilla.org/show_bug.cgi?id=342393 If you object to my age definitions, please place your comments and explanations in that bug. > Suggestions: > - Could there be a one touch link always present for "open > bugs assigned to me"? I realize I can make a search and > save it, but if there is "| My Requests |" and "| My Votes |" > shouldn't there also be a "| My Bugs |" too? There is, and in fact, it's lonely on its own line: Saved Searches: * My Bugs Unfortunately, how "my bugs" is defined varies with the type of person and how that person feels. If you can convince the community to change the definition, that's possible. However I doubt you'll be able to. http://defect.opensolaris.org/bz/editparams.cgi?section=query#mybugstemplate We're clearly not doing the best we can to advertise the feature, these two bugs come to mind: https://bugzilla.mozilla.org/show_bug.cgi?id=151802 https://bugzilla.mozilla.org/show_bug.cgi?id=345283 > - FIXINPROGRESS and so on are in ALL CAPS while almost > everything else is in a saner case. Can that be corrected? I'd strongly discourage admins from simply doing this. If you're going to do it, the best way is probably a "translation" and then letting people pick which they want. To do this, you'd clone the default and then change: /template/en/default/global/field-descs.none.tmpl, (it'd need to be maintained to actually list all the resolutions you have) Note: I haven't ever done this, so mkanat or someone might correct me. Resolutions/States are often viewed in buglists and I think one of the benefits of ALL CAPS is that while no all letters are equally wide in proportional fonts, they're at least evenly scanable (it's hard to explain). > - Description field not nearly big enough when filing bugs. This is trivial. Note that iirc in Bugzilla 3 when you click on the comment field it actually grows. I'm not sure if that happens w/ the Description field (if it doesn't, that's almost certainly a bug). I wouldn't know, as I use NoScript which means I don't experience any of those JavaScript behaviors most of the time. > - Filing bugs: Make "Platform" be "Any/Generic" instead of > "other" by default. I happen to own this code :|, It's designed to do user agent sniffing. However, if you don't want sniffing at all, that's simple: http://defect.opensolaris.org/bz/editparams.cgi?section=bugfields#defaultopsys http://defect.opensolaris.org/bz/editparams.cgi?section=bugfields#defaultplatform > - Sure would be nice to be able to look up people to assign > bugs to, etc. in a directory... is there integration with > a name service available? Right now if you enter a partial name (email address or real name), it'll try to get a match. dduvall made this change yesterday at my suggestion, for the record, that's: http://defect.opensolaris.org/bz/editparams.cgi?section=usermatch#usermatchmode = search http://defect.opensolaris.org/bz/editparams.cgi?section=usermatch#confirmuniqueusermatch = no There's an option which should *never* be enabled for a system with more than 10 users called usemenuforusers. It does not scale. Note: atm, the matching is done after you commit the bug (there's work to make this AJAX'd, I've seen it working), if there's only one match, it's simply chosen, if there are no matches, you get an error page, if there are multiple matches, you get a page asking you to pick a match. To guarantee an error so that you can search the directory, simply use the CC field and enter: "@ something", where "something" is what you seek and "@" is included with spaces around it to force an error. The other half, integration with directory services: yes, it's possible, however you have an open system which means you'd need to somehow support external LDAP account creation. http://defect.opensolaris.org/bz/editparams.cgi?section=ldap I don't know of a reasonable way to do this. For bugzilla.mozilla.org, we haven't switched to LDAP yet, but it's probably coming w/in 2 years (they've recently transitioned most other services to LDAP, although Bugzilla and the Wikis haven't yet :( ). As soon as it's done there, I'll certainly send a headsup, but if you guys do come up with a reasonable way of doing it, you might get it first in which case I'll send the headsup the other way (unless of course someone is nice enough to suggest it to upstream directly). > - In list view, bugs light up when I roll my mouse over them. > However, clicking does nothing until I remember that I have to > click on the bug number. Maybe the lightup-on-rollover should > go away? Seems like a false cue. This was discussed elsewhere. I don't want to repeat that discussion (it's in tools-discuss, I commented). I think perhaps the thing to do is fix the cursor and possibly switch from a background to a border. Those are both tweakable using css in the skin. - And if you like those changes, perhaps we can get them upstream, I'm not particularly fond of the confusion. I believe the general reason for the feature was to improve general scanning (but again, it's best to read the bugs, which I believe were referenced in the previous conversation). > - The default way to view a bug is called "showbug.cgi" but the > activity represented is really about "editing a bug". > These bugs are hard (for me) to read at a glance due to the > grid prisons[1] created by all of the text entry fields (many > of which are usually empty). Sure would be nice if the > default view was more streamlined, or if the text popped out > a bit better. Perhaps a button could activate editing mode. Try logging out. If this is what you want, something could easily be arranged. Beyond that, the Bugzilla UI has gone through a couple of refreshes recently. (I'm still amazed at how unused to the 3.1.2 look and feel I am.) > I also played with the "new charts" feature a bit and have some comments: > - Seems possible but hard to get a broad chart of say, all the > bugs in a category over time. So, you're already playing with: http://defect.opensolaris.org/bz/query.cgi?format=create-series I haven't. It's one of the few features with which I haven't played. I'd suggest you consider the newsgroup or irc channel as listed on http://www.bugzilla.org/support/ news://news.mozilla.org/mozilla.support.bugzilla (available via google groups and a mailinglist gateway) irc://irc.mozilla.org/mozwebtools > Overall: It's fine, but I wish it was a little more web-2.0-ey in its > approach to user interaction. We know, and people are working on it, but even Bugzilla customers are "change averse" :). _______________________________________________ tools-discuss mailing list tools-discuss@opensolaris.org
