Bug 291433: Ability to have custom fields whose visibility depends on the values of other fields

Patch By Max Kanat-Alexander <mkanat@bugzilla.org> r=bbaetz, a=mkanat

1 files changed, 4 insertions, 1 deletions

diff --git a/editfields.cgi b/editfields.cgi
index 138c6b729..e1c7d12c2 100644
--- a/editfields.cgi
+++ b/editfields.cgi
@@ -55,7 +55,6 @@ elsif ($action eq 'add') {
 }
 elsif ($action eq 'new') {
     check_token_data($token, 'add_field');
-
     $vars->{'field'} = Bugzilla::Field->create({
         name        => scalar $cgi->param('name'),
         description => scalar $cgi->param('desc'),
@@ -65,6 +64,8 @@ elsif ($action eq 'new') {
         enter_bug   => scalar $cgi->param('enter_bug'),
         obsolete    => scalar $cgi->param('obsolete'),
         custom      => 1,
+        visibility_field_id => scalar $cgi->param('visibility_field_id'),
+        visibility_value_id => scalar $cgi->param('visibility_value_id'),
     });
 
     delete_token($token);
@@ -107,6 +108,8 @@ elsif ($action eq 'update') {
     $field->set_in_new_bugmail($cgi->param('new_bugmail'));
     $field->set_enter_bug($cgi->param('enter_bug'));
     $field->set_obsolete($cgi->param('obsolete'));
+    $field->set_visibility_field($cgi->param('visibility_field_id'));
+    $field->set_visibility_value($cgi->param('visibility_value_id'));
     $field->update();
 
     delete_token($token);