Closed Bug 4889 Opened 25 years ago Closed 25 years ago

Request "Summary" be required field for new bugs

Categories

(Bugzilla :: Bugzilla-General, enhancement, P3)

enhancement

Tracking

()

VERIFIED FIXED
Bugzilla old

People

(Reporter: elig, Assigned: terry)

Details

I'd suggest that the "Summary" be added to the list of required fields for new
bug reports.


Why:

The only scenarios (from a two minute search through every browser bug in
Bugzilla) in which the field is blank are when either:
	(a) someone accidentally types the information into the Status Whiteboard or
URL field

	(b) someone is new to Bugzilla and really doesn't yet know how to use
Bugzilla.


By making this change:

In scenario (a), Bugzilla would be providing a useful "hey, did you really mean
to do that?" to the bug writer.

In scenario (b), Bugzilla would be teaching the novice bug writer how to use
Bugzilla.

Also, it would slightly reduce time wastage on the part of Bugzilla users, who
have to open up individual bugs that lack summary fields in order to determine
whether it's a significant bug or not. (e.g. after doing a query)
Yes, I agree this would be a good idea.
Reassigning to dmose@mozilla.org, who now has front-line responsibility for
all Bonsai and Bugzilla bugs.
Reassigning back to me.  That stuff about me no longer being the front-line
person responsible for Bugzilla and Bonsai turned out to be short-lived.
Please pardon our confusion, and I'm very sorry about the spam.
terry....I get a lot of blank Summarys from the net...could you implement this
one?
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
OK, done.
QA Contact: elig
Status: RESOLVED → VERIFIED
Verified fixed. Bug submissions are now rejected if the Summary text field is
blank. Thanks!
Moving to Bugzilla product
Component: Bugzilla → Bugzilla-General
Product: Webtools → Bugzilla
QA Contact: elig → matty
Target Milestone: --- → Bugzilla old
Version: other → unspecified
QA Contact: matty_is_a_geek → default-qa
You need to log in before you can comment on or make changes to this bug.