[Rt-commit] rtir branch, 5.0/use-core-custom-field-default-values, repushed

[Craig Kaiser]

The branch 5.0/use-core-custom-field-default-values was deleted and repushed:
       was a459b1a0dacc086a75864883749a014455501370
       now ca72703fd46dcdc32ffee00aae6cfb67a1120ee3

1: 9ff832aa ! 1: 0ee6b4d2 Use core default values instead of RTIR_CustomFieldsDefaults config
    @@ -10,7 +10,7 @@
      =item C<%RTIR_CustomFieldsDefaults>
      
     -Set the defaults for RTIR custom fields. Values are case-sensitive.
    -+Set the defaults value for Resolution if there is no value when ticket
    ++Set the default value for Resolution if there is no value when an RTIR ticket
     +is set to resolved or rejected.
      
      =cut
    @@ -41,7 +41,7 @@
     +    my $custom_field_defaults = RT->Config->Get('RTIR_CustomFieldsDefaults') || ();
     +    unless ( scalar keys %{$custom_field} ) {
     +        RT->Logger->error( "To set custom field defaults the %RTIR_CustomFieldsDefaults must be present, if there is a configuration for this value that was removed re-enable it and re-run this script." );
    -+        return;
    ++        die;
     +    }
     +
     +    foreach my $cf_name ( keys %{$custom_field_defaults} ) {
    @@ -57,7 +57,7 @@
     +            RT->Logger->debug( "Set default value for $cf_name to $custom_field_defaults->{$cf_name}" );
     +        }
     +        else {
    -+            RT->Logger->error( "Could not set default value for $cf_name custom field $msg" );
    ++            RT->Logger->error( "Could not set default value for $cf_name custom field: $msg" );
     +        }
     +    }
     +    RT->Logger->info( "Custom field defaults are now handled in the web UI on the custom field admin page, only Resolution needs to be set in \%RTIR_CustomFieldsDefaults." );
2: a459b1a0 = 2: ca72703f Update tests to reflect using core default CF values feature