When you accept a bug, you have to specify a milestone. This causes problems with products without milestones. In addition, there is nothing stopping a user from setting the milestone on acceptance and then changing it back to "---" after accepting it.
I believe there is a configuration option 'milestoneonaccept', but yeah I suppose it would cause problems. To start with, the notion of "blank milestone" is probably hardcoded to a specific name.
Priority: -- → P3
Target Milestone: --- → Bugzilla 2.18
Thanks for the tip on milestoneonaccept. I was getting really annoyed with this.
Created attachment 79749 [details] [diff] [review] v1 This disables the parameter 'milestoneonaccept' for products with only one (the default) milestone.
Targeting for 2.16 since we have a patch.
Target Milestone: Bugzilla 2.18 → Bugzilla 2.16
Nit: it should be part of the musthavemilestoneonaccept test, not the usetargetmilestone test. Gerv
Created attachment 79893 [details] [diff] [review] v2
Attachment #79749 - Attachment is obsolete: true
Comment on attachment 79893 [details] [diff] [review] v2 r= justdave
Comment on attachment 79893 [details] [diff] [review] v2 r=gerv. Gerv
Fixed. Checking in process_bug.cgi; /cvsroot/mozilla/webtools/bugzilla/process_bug.cgi,v <-- process_bug.cgi new revision: 1.125; previous revision: 1.124 done Gerv
Status: NEW → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.