enter_bug page

Gervase Markham gerv at mozilla.org
Thu Oct 17 13:25:49 UTC 2002

Jeff Hedlund wrote:
> Gervase Markham wrote:
>> It used to be the case that after you filed a bug, you had to click 
>> the link and wait for it to load before making any further changes. 
>> Now, the bug itself is output after the "bug added" message, so 
>> complaints in old bugs like "It is a multiple step process instead of 
>> one" no longer really apply.
> It still is a multiple step process, though.  

Any sufficiently-complicated change is going to be a multiple-step 
process, within the limits of an HTML GUI which isn't ridiculously 
crowded. For example, adding an attachment requires going to a separate 
screen. We should be aiming to have the most-used features accessible 
easily, and lesser-used features can require more clicks.

> I feel like anything that 
> an advanced user would immediately (and often) change upon entering the 
> bug should be [allowable] on the enter_bug page.  It reduces bug mail 
> and makes the entering of the bug a much simpler process.

It would have a negligible effect on volumes of bug mail (not much of my 
bug mail is from NEW bugs, at any rate), and if these users are 
"advanced", then they should be able to cope with "Here, I've filed my 
bug. Now, I want to change the dependencies, add a couple more CCs, 
ACCEPT it and set the priority."

> I actually patched 112373 in order to patch 
> http://bugzilla.mozilla.org/show_bug.cgi?id=141175.  So there are at 
> least two bugs for this feature (well, at least one requiring it).

But 141175: "Possibility to press a button on a bug thereby creating a 
new "sub-bug" that blocks the first bug."

I'm afraid that I think this is another terrible idea :-| This again 
goes against the rule of making the common things easily accessible and 
letting the less common things take more clicks. This is an action which 
I doubt I'd use more than once a month - it certainly doesn't justify 
having UI to reduce it from:
"Click "Enter Bug", fill in fields, click "Commit", edit dependencies, 
click "Commit"
"Click "Enter Bug Which Blocks This Bug", fill in fields, click "Commit".

Given that the filling in the fields is the time-consuming issue here, 
you have saved very little time and yet complicated the show_bug screen, 
which is already too complex.

This bug could be fixed for installations that want it, when process_bug 
and post_bug are combined, using a simple HTML link, without any 
additional code. I don't think that it should ever be fixed in core 
Bugzilla, and certainly doesn't justify the 112373 patch.

> I'd like to keep the 112373 patch in, so that 141175 can be patched.  I 

I'd like to back 112373 out, and mark 141175 as WONTFIX :-)


More information about the developers mailing list