Skip navigation.

Bugzilla to get a facelift next week

Bugs
Bugs

Our much beloved bugzilla is getting a face lift this upcoming week. Those wanting a sneak peak at Olav Vitters' incredible work can point their browsers at http://bugzilla-test.gnome.org/.

Feel free to try stuff out on that site (changing bugs, adding patches, or whatever), as it just has an old copy of the database and email is not hooked up. We'd like to get a bunch of people to test it to make sure it's solid when we switch over next week. (Note that you can use your normal bugzilla login and password). Also, make sure to tell Olav (who goes by the nick 'bkor' on irc.gnome.org) how cool he is for all the work he has done.

More details about the change (when it'll happen, what has changed, etc.) can be found in his recent email to d-d-l.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Excellent, but one more request

This looks fantastic! I always thought gnome bugzilla was the best designed bugzilla around and now it's even better.

One small request though:
Is there any chance the bug list pages could have a link to the bug reports which is easily accessible. When I read a bug title I often want to open the bug by clicking. Unfortunately I have to track across the screen to the bug number column, which wastes valuable seconds. It would be great if the summary text was also a link to the report (or even the whole line was a link). If you don't like having such long links for whatever reason, perhaps you could place a little unobtrusive bug icon right next to the bug title which would link to the report itself. If you disagree, I'd love to hear your thoughts.

ps: is there any chance of your customisations making it into the core bugzilla distribution (hopefully set as default!). It would be great if all your hard work could show up everywhere.

For clicking the summary I

For clicking the summary I have to see what others think. I have a habit of double clicking randomly on a page (selecting text). Having the summary clickable would be pretty annoying in the beginning. But I'll see what others think. If they agree I'll change it. I do remember a Bugzilla bug (upstream) about making the entire line clickable. That was rejected for such a reason (but only summary seems sane though).

I will try to get as many changes into the core/upstream Bugzilla distribution as I can. I still have to finish one of the patches for Bugzilla 2.22 that lots of the changes depend on. It does require some extra work, but it also benefits us as it will make upgrading to a newer Bugzilla easier for GNOME (this upgrade was around 6 months of work). Bugzilla 2.20 has a lot of features not needed by GNOME that I fortunately could ignore when making the changes, but I do believe these changes are possible (many of them are already filed upstream).

Blocked links (HTML4 and CSS2)

I like the design, it seams very easy to use.

The only suggestion I have is to use
display: block;

in the stylesheet for the links
* Short Bug Search Form
* Complicated Bug Search Form

at Search.

Having to press on the exact text link is very HTML3 =)

A good example of blocked links is the manu at the left at Fedora

Nice suggestion. Unfortunately display: block is not enough

I tried adding a 'width: 100%' to the css, but didn't work. Will try to fix that. Appreciate if you have a suggestion to fix that...

Move the padding

... to an element inside the table/a element?

Thanks

So simple but looked over the cellpadding on the table. Is fixed now.

Just one little request

Can we have those nice little icons in the username/password fields, like on art.gnome.org?

Done :)

Good suggestion! Wanted to use Tango icons, but couldn't find user/password icons.

User Info page

The User Info overview page is great, particularly for maintainers. Well done.

Next / previous bug? by Anonymous George

Please give rationale for feature requests

but it appears to me that the people who have done these changes have not really used Bugzilla. Otherwise they would not attempt to remove essential features.

There may be a valid point to your sentiment, but it would really help if you could explain it instead of merely attempting to take a pot shot at others. You haven't stated how much you use bugzilla, in which ways you use it, nor how this particular feature is actually helpful to your particular use cases. You also cast a lot of doubt on your comments by your claims that "the people making these changes have not really used Bugzilla"; anyone who does in fact use it as much as we have (a) know exactly who we are and would refer to us by name (or more likely just talk to us on IRC) and (b) know that we use bugzilla very heavily.

Now, of course, Olav and I might have different use cases than others--mostly because we use it more than most people. If you find something that you think should be different, please explain why and how it would be helpful.

Why the next/back were usefull

Note - I am not the original poster.

I use bugzilla infrequently, and that's why I found the next/back buttons useful.
I could request all unconfirmed bugs of a product I'm familiar with, and start going over them - Any bug I could confirm I would (and possibly mark as new), those I couldn't confirm I would note so.
I would often bump into bugs I couldn't (or wouldn't) test. For example, 64 bit specific bugs, or bugs that would take too much time to reconstruct. In such a situation, it would be useful to use the "next" button to skip the current bug, and continue working.

If I wanted to use a similar strategy now, how should I do that? I am aware that Bugzilla should move me to the next bug after changing the current, but what if I don't change the current bug at all? What options do I have to get to the next bug, other than going back in my browser to the result list, then going forward (which would be slower and more complicated)?

Yours,

Uri David Akavia

Yeah probably very different way of working

I usually open many tabs because Bugzilla is so slow (I consider 0.1 secs acceptable ;). Then I start investigating each bug, searching for dupes etc. Every time you search the next/back list is 'replaced' (stored in a cookie). Makes the entire Next/Previous thing annoying.

Also having 'This bug is not in your last search results'.. my reponse usually is 'because you forgot them'!

I assume no-one uses anything other than the Next/Prev buttons.. have to see if I can put them someplace where they do not annoy me, while still being useful for the persons that use them.

You might be right

You might be right (after reading your answer), but I'm glad that you are open to other opinions.

Also, since I didn't say this before:
THANK YOU!
I played around with the new Bugzilla and it seems very useful - very nice options for maintainers and users.
I like the new color scheme as well (I read people complaining).

Thank you,

Uri David Akavia

They are useless

> but it appears to me that the people who have done these
> changes have not really used Bugzilla

Elijah and me think they are useless. They are not reliable and pretty much suck.

Elijah has closed 8506 bugs. I did 1279. Unless your name is Gerardo Marin I doubt you closed more.

wow by Anonymous George

He didn't ask what improvements where made

He didn't ask what improvements where made. From the article:
> More details about the change (when it'll happen, what has changed,
> etc.) can be found in his recent email to d-d-l.

So see http://mail.gnome.org/archives/desktop-devel-list/2005-December/msg00057.html

I think it is pretty clear I won't undo this (I mean upgrading Bugzilla). Note that facelist includes more than just making it look different. That is a very very small part of this change.

No need to ask questions already answered ;-)

What actual improvements were made

You could have answered that question by reading the link provided in the article. ;)

where/why have the back/forward buttons gone?

You could have answered that question by reading Olav's response. They were removed.

Cheers,
Elijah

Font sizes by Anonymous George

Oops, it's not just a facelift

Perhaps I picked the wrong wording in calling this a "facelift", considering from the comments here so far. There are lots of new, awesome features and bug fixes. See the link in the article to the d-d-l email.

Anyway, back to the topic of your post, I don't even much notice the font change Olav had made while testing stuff out until others had brought it up in regards to the title of bugs on show_bug.cgi (which has since changed). It's possible that this is browser related (as it was for the title of bugs on show_bug.cgi), or just that user preferences are very different (Olav was really annoyed at the old font size, I'm not bothered by either size, and you seem to dislike the new one). If there are enough comments on the issue, we may try to figure out a user preference or something. Haven't really heard much about this issue from other people that have commented, though. *shrug*

Font sizes by Anonymous George

Sort-of agree

I did wonder if I should change the font settings or just change my browser settings. Changing the font sizes do make having the browser font size preferences pointless. But almost every site that I visit already change the font settings. Some do this in such a way that my fonts will be too tiny if I change them. To deal with these sites users already have to use some sort of never-change-my-fonts setting or user css.

So my conclusion was to change the font settings. The new bguzilla will have 'bugzilla-gnome-org' as the body class setting (currently bugzilla-test-gnome-org) for persons wanting to change the layout. Using that and user css you can change the settings to whatever you want.

I see. Everybody is on crack by Anonymous George

Yes

.

PS: I do not pretend. I am on crack.

I agree with the parent post

I agree with the parent post on this. The font size is too small and should be changed to match what is currently on b.g.o.

Hu? You argee bkor is on

Hu? You argee bkor is on crack! How awful.

Bkor: come to my office on Monday, we will have a session to solve your problem.