Closed
Bug 45043
Opened 24 years ago
Closed 12 years ago
in enter_bug.cgi, want the Version selected to be a settable parameter
Categories
(Bugzilla :: Creating/Changing Bugs, enhancement, P3)
Bugzilla
Creating/Changing Bugs
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: cbegle, Unassigned)
References
Details
(Whiteboard: enter_bug)
bugzilla v. 2.11 We would like that the Version in the bug entry form to be one of the settable parameters. This would allow me to set the default version to the most likely value, so Bugzilla would select that value instead of the first value in the Version list. This would make this field more useful for the users of our system.
Updated•23 years ago
|
Target Milestone: --- → Bugzilla 2.16
Comment 2•23 years ago
|
||
-> Bugzilla product, Enter-Bug component, reassigning.
Assignee: tara → myk
Component: Bugzilla → Creating/Changing Bugs
Product: Webtools → Bugzilla
Version: other → unspecified
Updated•23 years ago
|
Whiteboard: enter_bug
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
Updated•21 years ago
|
Severity: normal → enhancement
OS: Windows NT → All
Hardware: PC → All
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
Assignee: myk → create-and-change
QA Contact: mattyt-bugzilla → default-qa
Target Milestone: Bugzilla 2.22 → ---
We just got a request for this type of functionality: https://bugs.eclipse.org/bugs/show_bug.cgi?id=243417
This bug is almost 10 years old. Don't you think it's time it got fixed?
Comment 9•12 years ago
|
||
I don't think a default version will help. It's wrong to assume which version of your product a user is using and it will still require the QA team to check this information. If the user doesn't specify any version, then it would be better to fall back to some "unspecified" value, which you are free to add at the end of your version list.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WONTFIX
Comment 10•12 years ago
|
||
> It's wrong to assume which version of your product a user is using
That may be the case for some products, but not for all. I know that most users of our product use the latest officially released version. Setting that one as default would make most bug reports correct and neither reporter nor triager have to waste time fiddling around with this field.
We know this field is not 100% trustworthy, and we'd rather go with a solution that is 90% correct than with a solution that is 0% correct and causes unnecessary work (default to "undefined") or the current solution that is 10% correct and also causes unnecessary work (default to latest version, although that's not yet released).
You need to log in
before you can comment on or make changes to this bug.
Description
•