Description of problem:
As part of the JIRA migration several new custom fields will need to be created that are going to be visible only for certain products. Several of the products will need to have a different list of values visible based on the product in the select field. We need to have support in Bugzilla to allow turning on or off certain values for a given custom field so we do not need to create multiple custom fields in order to have different lists.
Assigning to contractor as part of his work estimate.
You know, actually, it might be possible to just have the extension adjust the list of legal values before parsing the template, in which case we wouldn't need to do this. In fact, I think it would be simpler to just have the extension hack it.
*** Bug 588602 has been marked as a duplicate of this bug. ***
Assigned to Dave Lawrence to verify/QA. https://bz-web2-test.devel.redhat.com/
Changes are in place now to support this although it requires going in and actually cleaning up the fields that are already there to so that they only show up for products they are required for. I will need to talk to the different partner/program managers to start performing this clean up. So for now all custom
fields are still enabled for all bugs. So please don't think the show_bug.cgi page will have all of the fields displayed permanently.
Can this bug be closed?
The target release changes are tracked with bug 587798.
I am not aware of any other fields that need to be specifically product based. Please let me know if this is not the case.
Clean-up task from the March 9 2011 Bugzilla / BRMS Pilot Meeting
This bugzilla has been marked as verified - 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!
As per meeting discussion, this requires someone to test it before going to VERIFIED
per our call today, the only customer filed to be verified is target release changes and is tracked with bug 587798. Once 587798 is verified/closed, we can also close this bz 599237.
As per comment #9, this bug is now CLOSED :)