This is split off bug 16775. See my 2001-01-12 08:33 comment there: * Bug Settings / Module Options: Well, in my view Platform/OpSys and Product/Component are more closely related than e.g. Platform/OpSys and Status/Resolution. Where is the logical division between fields about the bug itself (Product/Component/Platform/ OpSys) and fields about the process of fixing it (Severity/Priority/Status/ Resolution)? Ok, arguably severity could belong to both. Summary, URL, would logically belong to the first group, Status Whiteboard, Target Milestone, Votes to the second. But it's probably not wise to tear the text fields apart. ------- Additional Comments From NeTDeMoN - Brian Bober 2001-01-12 14:03 ------- I believe you are saying [...] that you think there is no logical division between the fields on Bugzilla. Although I couldn't move all the fields around, I think that is valid and something that should be looked into for future versions of Bugzilla. Perhaps you could submit a bug on that if one doesn't already exist. I personally think bugzilla should be changed eventually to look more like www.redhat.org/bugzilla, but if I changed that on query.cgi, all of bugzilla would have to be changed. =============================================================================== This bug is about splitting the query form into (at least) two parts: (1) information about the bug itself, and (2) information about the bug fixing process. The second part is usually unnecessary if you are searching for bug reports you've never seen before, and thus should be hidden behind a "more options" link by default for beginners. For the origins of this idea, see bug 16775 (again): ------- Additional Comments From spyysalo@cs.helsinki.fi 1999-10-19 12:45 [...] - Forget about the Platform, OpSys, Priority, Severity, Program, Version, Component and Target Milestone fields to get started. If you're just looking for possible earlier reports for a bug you can do without those fields just fine.

Look at query redesign issues due 2.16.

Mass moving to new product Bugzilla...

We are currently trying to wrap up Bugzilla 2.16. We are now close enough to release time that anything that wasn't already ranked at P1 isn't going to make the cut. Thus this is being retargetted at 2.18. If you strongly disagree with this retargetting, please comment, however, be aware that we only have about 2 weeks left to review and test anything at this point, and we intend to devote this time to the remaining bugs that were designated as release blockers.

I think this got fixed as part of bug 98707... any dissenters?

I agree with Dave: the logical split (per this bug's summary) has been done with the query page redesign. The role of hardware/os etc. is still debatable, but also heavily depends on the product being developed - there is much room for installation-wise template customizations here too. Unless there are more generic development ideas (particularly related to this bug), I think we can close this out.

Yes, the logical split is not perfect (the bug itself vs. bug-fixing process) but I think it's usable as-is, and I currently have no suggestions for a different split. IMO there are two things left: 1) The option to hide everything but the first part of the form on the query page so that only the part from "summary" to "keywords" is visible (or even only up to "The URL", hiding status whiteboard and keywords field, too), maybe with a (modified?) "bug status" control a la attachment 22470 [details] in bug 16775 ("[RFE] optional simplified version of query.cgi"). 2) Some easily findable online user-documentation (online-help) for the query form should state that if you are looking for a bug you haven't seen yet (e.g. when looking for already existing bugs before filing a dupe), then you don't need to worry about anything besides the first part of the query form. Issue 1) could be dealt with in bug 16775, if so desired.

Enhancements which don't currently have patches on them which are targetted at 2.18 are being retargetted to 2.20 because we're about to freeze for 2.18. Consideration will be taken for moving items back to 2.18 on a case-by-case basis (but is unlikely for enhancements)

Bugzilla 2.20 feature set is now frozen as of 15 Sept 2004. Anything flagged enhancement that hasn't already landed is being pushed out. If this bug is otherwise ready to land, we'll handle it on a case-by-case basis, please set the blocking2.20 flag to '?' if you think it qualifies.

Nobody dissented from justdave's comment 4, which means that this bug was handled by bug 98707. Andreas, you can file your comment 6 stuff as a new bug, if you still think it's an issue, and it hasn't been filed. *** This bug has been marked as a duplicate of 98707 ***