Description of problem: Show deny message when move a bug to other product and select more than one component. The Bugzilla product does not allow a bug to be assigned more than one component. Version-Release number of selected component (if applicable): 4.4.6026-3 How reproducible: Always Steps to Reproduce: 1.find a bug whose product doesn't allow multi components, like bugzilla bug 2.Update this bug, change product to "JBoss Operations Network"(which allow multi components), click button "save changes", then select any 2 components of product "JBoss Operations Network", make sure version, target milestone, target release selected 3. click button "commit" Actual results: The Bugzilla product does not allow a bug to be assigned more than one component. Expected results: Don't show deny message, since the product "JBoss Operations Network" allow mutli components Additional info:
Seems closely related to Bug 1136687. They should probably be fixed together.
Also can't update bug to multiple components by xmlrpc
Seems to be a small regression related to the rewrite of the multivalue extension. It appears to be checking whether the old product supports multiple values rather than new product.
Tested on QA environment(bzweb01-qe) with version(4.4.9033-1, DB: mysql) QA environment(bzperfweb01.app.qa) with version(4.4.9033-1, DB: psql ) Result: Most parts works fine, but below 2 errors need to be fixed the better. Steps: 1. Open a bugzilla product bug(which doesn't support multi_component) 2. Select product 'JBoss Enterprise Application Platform 6'(which support multi_component), then choose 2 components(like: Build, CLI), then click button 'Save Changes' 3.Error_1: only 1 component marked as selected status in the current page 4. Return back by click the browse's "<-" 5.Error_2: in the bug detail page, product value is shown as "Boss Enterprise Application Platform 6", but the component value is shown as the original bug's component(same as step 1) It should shown as components: Build, CLI
Note this solves the #3, which is a bug in production and not related to this change. I cannot reproduce #5.
Seems https://code.engineering.redhat.com/gerrit/#/c/48089/ didn't merged to build 4.4.9033-2, QE waiting for new build.
(In reply to Jeff Fearn from comment #5) > Note this solves the #3, which is a bug in production and not related to > this change. > > I cannot reproduce #5. #3 fixed in build 4.4.9033-3, but #5 still could be reproduced. Do u clicked the 'go back' button of browser?
(In reply to qgong from comment #7) > (In reply to Jeff Fearn from comment #5) > > Note this solves the #3, which is a bug in production and not related to > > this change. > > > > I cannot reproduce #5. > > #3 fixed in build 4.4.9033-3, but #5 still could be reproduced. > Do u clicked the 'go back' button of browser? Yes I clicked the back button and the fields stayed as I'd entered them. Firefox 31.5.0, RHEL6.
(In reply to Jeff Fearn from comment #8) > > Yes I clicked the back button and the fields stayed as I'd entered them. > > Firefox 31.5.0, RHEL6. As we know, the latest stable firefox version is 38.0.1, So I suggest you use a latest version firefox to test check it again, and this error also happend in google-chrome(42.0). Anyway, this #5 is just a small usability issue, QE think it is acceptable to file another low severity bug to track this issue and not blocking current bug any more.
I updated to FF 38.0 on RHEL6 and I still can't duplicate #5.
It is incredible, that #5 could not reproduced in one of my test workstation. Verified this issue on build 4.4.9033-5, Pass
This change is now live. If there are any issues, do not reopen this bug. Instead, you should create a new bug and reference this bug.