Community
Participate
Working Groups
It seems that the default look of Bugzilla that comes with Bugzilla 3.0 is broken under some circumstances. I'll attach a screenshot. In general, it would be very useful to make a few changes to the templates in order to streamline our workflows. For example, for about anything that I usually do to a bug, I have to scroll the page even though I have 1600x1200 pixels available to me. Assuming that the webmaster is not keen on working on the Bugzilla templates, what is the best way to make progress on this?
Sorry, I lost my clipboard contents with the screenshot while entering this bug. I will attach the screenshot next time it happens (parts of the page overlap other parts). My comment about optimizing the workflows is still valid. Any comments or ideas?
Created attachment 76003 [details] screenshot Here it is, it happened when adding the dependency to the parent bug.
fwiw, the templates used by bugzilla.mozilla.org look much nicer than ours. No ugly borders around everything, cleaner header, things align properly... If you could point me at the template files we use, and ideally the ones used by bugzilla.mozilla.org, I would be happy to invest a couple hours on this to see what can be done.
> If you could point me at the template files we use, and ideally the ones used > by bugzilla.mozilla.org, I would be happy to invest a couple hours on this to > see what can be done. I'm not sure about the templates on bugzilla.mozilla.org, but we use the stock Bugzilla template. Your best bet is to download and install Bugzilla 3.0, then submit patches from there. FWIW, the Bugzilla team is working on a better/cleaner default skin via this bug: https://bugzilla.mozilla.org/show_bug.cgi?id=259723
(In reply to comment #3) > If you could point me at the template files we use, and ideally the ones used > by bugzilla.mozilla.org, I would be happy to invest a couple hours on this to > see what can be done. I searched the Mozilla CVS up and down at least 3 times to find them because I also like them MUCH better than the stock 3.0 templates. However, no luck here. I could imagine that an Eclipse.org Bugzilla skin could become a Phoenix component where people contribute, submit patches and gain commit rights. However, to be successful we would need a Bugzilla sandbox (something like landfill) where the skin is automatically deployed too on every check-in. Denis, do you think we can create something like this? I understand that this would mean yet another database on the DB server but the assumption is that this would be a plain Bugzilla sandbox with no guaranteed uptime or history.
(In reply to comment #5) > I could imagine that an Eclipse.org Bugzilla skin could become a Phoenix > component where people contribute, submit patches and gain commit rights. I would see this as the logical path as well. It would also ensure that any submitted content can be maintained in the open. > However, to be successful we would need a Bugzilla sandbox (something like > landfill) where the skin is automatically deployed too on every check-in. > > Denis, do you think we can create something like this? I understand that this > would mean yet another database on the DB server but the assumption is that > this would be a plain Bugzilla sandbox with no guaranteed uptime or history. > Phoenix has a project vserver, so if this new Phoenix component is created, then I can set up the repository to simply publish changes to a BZ sandbox on the vserver. I'm not sure if we can put Bugzilla templates in CVS, though. [%# The contents of this file are subject to the Mozilla Public # License Version 1.1 (the "License"); you may not use this file # except in compliance with the License. You may obtain a copy of # the License at http://www.mozilla.org/MPL/ I'll open a discussion ticket on IPZilla.
> I'll open a discussion ticket on IPZilla. https://dev.eclipse.org/ipzilla/show_bug.cgi?id=1697
*** Bug 200718 has been marked as a duplicate of this bug. ***
FWIW, the problem with the broken UI/collapsed boxes when committing a change to a bug has been fixed in the just-released Bugzilla 3.0.1. See this bug: https://bugzilla.mozilla.org/show_bug.cgi?id=370739
Also, before diving into skin customizations, let's have a look at the 3.2 preview site: https://landfill.bugzilla.org/bugzilla-tip/ That's their test site, which is pulled straight from CVS' HEAD, so don't expect everything to work perfectly or to be polished. But it does show the UI work the team are doing for 3.2.
(In reply to comment #10) > Also, before diving into skin customizations, let's have a look at the 3.2 > preview site: > > https://landfill.bugzilla.org/bugzilla-tip/ > > That's their test site, which is pulled straight from CVS' HEAD, so don't > expect everything to work perfectly or to be polished. But it does show the UI > work the team are doing for 3.2. What is the time frame for this, i.e. when do you think this version can be deployed at eclipse.org? While it looks nicer for sure, it still has the same usability problems. The most annoying problem is that you have to scroll down for almost anything you do since the commit button is below the attachments.
(In reply to comment #11) > What is the time frame for this, i.e. when do you think this version can be > deployed at eclipse.org? Well, we'd have to wait for them to release Bugzilla 3.2 first, so that will be several months. If putting a second Commit button (higher up) is all that's needed to create some happiness here, I can do this for you. Simply paste a Bugzilla screenshot with a red X to mark the spot of where the second Commit button should be and I'll wave some magic around.
(In reply to comment #10) > That's their test site, which is pulled straight from CVS' HEAD, so don't > expect everything to work perfectly or to be polished. But it does show the UI > work the team are doing for 3.2. I'm not convinced from that idea. AFAIK the skin work mainly concentrates on CSS changes. Although, we should look for usability enhancements. Some may be addressed by the Bugzilla team and we may find patches in their Bugzilla. But we should also not be scared of creating and submitting patches ourselves.
(In reply to comment #9) > FWIW, the problem with the broken UI/collapsed boxes when committing a change > to a bug has been fixed in the just-released Bugzilla 3.0.1. > > See this bug: https://bugzilla.mozilla.org/show_bug.cgi?id=370739 > I've upgraded to Bugzilla 3.0.1, so the broken boxes should be fixed. I haven't see it since. Boris?
Yes, the broken boxes are fixed, but the usability problems remain. Updating the summary accordingly.
Just fyi, Mylyn has an Eclipse.org specific Bugzilla plug-in that it currently redistributes (includes template for bugs.eclipse.org repository, duplicate detector, and create bug from Error Log action). The Mylyn project would be happy to take additional requests to make Eclipse committers' experience with it's rich UI to Bugzilla easier, and the editor is extensible to repository specific extensions (e.g. to support things like bug 194606).
I should add that Mylyn's bug reporting facilities are currently included with every EPP packaging other than CDT. For Europa the plug-in that automatically adds bugs.eclipse.org as a repository is currently excluded from the Java distribution due to a dependency on PDE Runtime, but we plan on moving that. So I expect that an increasing number of bug reports will come from within Eclipse than from the web UI, which I see as a good opportunity to improve the rich UI to make committers' and triggers' life easier. Based on my experiences with the Bugzilla sources, if you go beyond template customization it is way easier to extend Mylyn's Java/Forms based code than Bugzilla's Perl/HTML/JS :)
Bugzilla 3.4, which I will install this weekend, has a significantly better UI. Let's re-evaluate this bug once we've upgraded.
We'll be deploying BZ 4.0 in a few weeks. If anyone thinks there are serious issues with the UI, we could work with BZ to help fix them. Otherwise, I think for the most par it just works. Since this bug was opened the BZ UI has evolved nicely. Closing as WONTFIX. Please reopen if you feel strongly otherwise.
