Closed
Bug 98439
Opened 23 years ago
Closed 14 years ago
Don't just choose first option as a default.
Categories
(Bugzilla :: Bugzilla-General, enhancement, P3)
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: CodeMachine, Unassigned)
Details
We need to make sure that default options (ie the first one) are not chosen where none is sensible. For example, versions on bug reporting and most options on the bug product change page.
Comment 1•23 years ago
|
||
I think what Matty means is that things like version and maybe a few other fields (OS comes to mind, since the current thinking is that the OS version shouldn't be reported in the UA sting, and it's already extrement inaccurate for Macs for that reason) should not have a default value, and the bug entry code should warn them when they try to enter a bug without setting it. This will increase the usefulness of these fields because the user is forced to actually set them instead of just accepting the default (even though the default may be wrong) Is that correct, Matty?
Reporter | ||
Comment 2•23 years ago
|
||
That's what I said, yes. =)
Reporter | ||
Updated•23 years ago
|
Priority: -- → P3
Target Milestone: --- → Bugzilla 2.16
Comment 3•23 years ago
|
||
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.
Target Milestone: Bugzilla 2.16 → Bugzilla 2.18
Reporter | ||
Updated•21 years ago
|
Severity: normal → enhancement
Comment 4•20 years ago
|
||
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)
Target Milestone: Bugzilla 2.18 → Bugzilla 2.20
Comment 5•20 years ago
|
||
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.
Target Milestone: Bugzilla 2.20 → Bugzilla 2.22
Comment 6•19 years ago
|
||
Reassigning bugs that I'm not actively working on to the default component owner in order to try to make some sanity out of my personal buglist. This doesn't mean the bug isn't being dealt with, just that I'm not the one doing it. If you are dealing with this bug, please assign it to yourself.
Assignee: justdave → general
QA Contact: mattyt-bugzilla → default-qa
Comment 7•14 years ago
|
||
Severity, priority, platform and OS fields have defaults on purpose. We shouldn't force the user to edit them (aka "make it easy to file a bug"). The target milestone also has a default value, and shouldn't be set by the reporter, most of the time. The version being wrong is not a big deal, and by default, it uses the last used version, which is most of the time accurate as you don't use a new version every day. So I see no benefit in implementing this RFE.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•