Closed Bug 125066 Opened 22 years ago Closed 22 years ago

Have to set milestone when accepting bug

Categories

(Bugzilla :: User Interface, defect, P3)

Product:
Bugzilla
Component:
User Interface
Version:
2.14
Platform:
Sun
Solaris
Type:
defect

Tracking

()

Status:
RESOLVED FIXED
Milestone:
Bugzilla 2.16

People

(Reporter: mozilla-work, Assigned: myk)

Details

Attachments

(1 file, 1 obsolete file)

v2
723 bytes, patch
justdave
: review+
gerv
: review+
Details | Diff | Splinter Review 
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.
Attached patch v1 (obsolete) — — Splinter Review 
This disables the parameter 'milestoneonaccept' for products with only one (the
default) milestone.
Targeting for 2.16 since we have a patch.
Keywords: patch
Target Milestone: Bugzilla 2.18 → Bugzilla 2.16
Nit: it should be part of the musthavemilestoneonaccept test, not the
usetargetmilestone test.

Gerv
Attached patch v2 — — Splinter Review 

        Attachment #79749 -
        Attachment is obsolete: true

    
    

    
  
Comment on attachment 79893 [details] [diff] [review]
v2

r= justdave

        Attachment #79893 -
        Flags: review+

    
    

    
  
Comment on attachment 79893 [details] [diff] [review]
v2

r=gerv.

Gerv

        Attachment #79893 -
        Flags: review+

    
    

    
  
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
Closed: 22 years ago
Resolution: --- → FIXED
QA Contact: matty_is_a_geek → default-qa

          You need to log in
          before you can comment on or make changes to this bug.