When Bugzilla is able to support multiple affected versions, the product browser will need to be updated to support displaying the lists properly. \ Thoughts: If a bug is in multiple versions will it be once for each version in the version tables?
Hi Kevin, When Noura implemented the target release code (bug 584956) she had a one-to-one relationship between bugs and releases (using the bugs.release column). Unfortunately this needs to be a many to many relationship (https://bugzilla.redhat.com/show_bug.cgi?id=584956#c23) I see two possible ways to solve this (1) Add a new joining table to create a many to many relationship (and remove bugs.release column) and make the necessary changes to the UI. (2) Hack together a new custom field, and fake the changes in the UI. To me solution (1) is a little extra work, but is going to much more maintainable in the long run. What are your thoughts? -- simon
Just to clarify the new column was actually bugs.target_release (not bugs.release as mentioned above)
(In reply to comment #3) > I see two possible ways to solve this agree option (1) is the better. Please create an upstream bug and attach our patch.
Bugfix (showing the correct information for those that cannot edit bugs, and fixes for the import scripts. $ svn commit Bugzilla bugzilla.spec.in template/ Sending Bugzilla/Bug.pm Sending Bugzilla/Migrate/JIRA.pm Sending Bugzilla/Migrate.pm Sending bugzilla.spec.in Sending template/en/default/bug/edit.html.tmpl Transmitting file data ..... Committed revision 2362.
This code is now live on bz-web2-test.d.r.c. The import that I am currently doing will populate this field. -- simon
kbaker: Regarding creating a bug and submitting it upstream, are Mozilla still accepting patches for new functionality for bugzilla 3.6? Or are we best to wait until we migrate to 4.0?
Clean-up task from the March 9 2011 Bugzilla / BRMS Pilot Meeting This bugzilla has been marked as ON_QA - we need to verify that the changes made to https://bz-web2-test.devel.redhat.com/ are acceptable and that this bugzilla can be closed. Please verify the change and close (or re-open) this bugzilla by March 15 2011. Thx!
I'm sending this back to ON_DEV. The "Version" field doesn't accept two different versions, as evidenced by https://bz-web2-test.devel.redhat.com/show_bug.cgi?id=680246 (When submitting 5.0.2 and 5.1.0.GA, only 5.0.2 is selected after the form is refreshed.) Also, this is a problem for the data import - the JIRA in question has two versions in the "Affects" and this bug only displays one.
The "Target release" isn't copied properly, as evidenced in https://bz-web2-test.devel.redhat.com/show_bug.cgi?id=713079. While the original JIRA has "One off releases" there, in Bugzilla nothing is selected. The same issue appears here also: https://bz-web2-test.devel.redhat.com/show_bug.cgi?id=BRMS-564 The difference is that this bug is supposed to have multiple "Target release" selected. For that reason, it is directly related to this bug. Returning to development as it is not possible to verify this.
This will be fixed when the current migration import is complete on bz-web2-test.d.r.c.
Please see: https://bz-web2-test.devel.redhat.com/show_bug.cgi?id=730537 I updated it so that it has three values selected in the "Version" field - "5.1.0.GA", "BRMS 5.1.1.GA" and "BRMS 5.2.0.GA". However, in the product browser (https://bz-web2-test.devel.redhat.com/page.cgi?id=browse.html&tab=components&product=JBoss+Enterprise+BRMS+Platform&bug_status=all#version), the following is not even listed: "BRMS 5.1.1.GA" When I click on "BRMS 5.2.0.GA", the bug in question does not appear on that list. Assigning back to Simon.
(In reply to comment #19) > However, in the product browser > (https://bz-web2-test.devel.redhat.com/page.cgi?id=browse.html&tab=components&product=JBoss+Enterprise+BRMS+Platform&bug_status=all#version), > the following is not even listed: "BRMS 5.1.1.GA" > > When I click on "BRMS 5.2.0.GA", the bug in question does not appear on that > list. Both issues are fixed. > Assigning back to Simon. Marking bug as ON_QA. -- simon
This change went live as part of the updated last Thursday (EDT). -- simon