Bug 921812 - Milestone could be multiple selected on the bug page
Summary: Milestone could be multiple selected on the bug page
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Bugzilla
Classification: Community
Component: Creating/Changing Bugs
Version: 4.4
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: 4.4-3
Assignee: Simon Green
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-03-15 01:43 UTC by wangjing
Modified: 2018-12-09 06:29 UTC (History)
2 users (show)

Fixed In Version: 4.4-3
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-05-20 11:04:33 UTC
Embargoed:


Attachments (Terms of Use)

Description wangjing 2013-03-15 01:43:00 UTC
Description of problem:
*target milestone* field could be multiple selected on the bug page of product 'Jboss Operations Network'

Version-Release number of selected component (if applicable):
version 4.4.rc2-2.b01 on QE test env.

How reproducible:
always.

Steps to Reproduce:
1.on the page of adding a new bug of product 'Jboss Operations Network', check the field *target milestone*.
2.on the existed bug page of product 'Jboss Operations Network', check the field *target milestone*.
3.
  
Actual results:
both of the two pages in step1/2, the field *target milestone* could be multiple selected.

Expected results:
both of the two pages in step1/2, the field *target milestone* could not  be multiple selected.

Additional info:

Comment 3 wangjing 2013-05-07 10:53:35 UTC
Verified on qe test env version 4.4.rc2-3(20130426) --> PASS

Verify steps:
1.on the page of adding a new bug of product 'Jboss Operations Network', check the field *target milestone*. 

then expected result: the field *target milestone* could not be multiple selected.

2.on the existed bug page of product 'Jboss Operations Network', check the field *target milestone*.

then expected result: the field *target milestone* could not be multiple selected.

Actual results:
same as the expected results above.


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