[Rt-commit] rt branch, 4.6/custom-date-ranges, repushed

[? sunnavy]

The branch 4.6/custom-date-ranges was deleted and repushed:
       was fd018fe2e5387720cf5364091409984c1cda9229
       now b6822facbfe6f51da0154432d13e58a67ef83c9e

 1: a748c477e !  1: b80275e1d RT::Record support for CustomDateRanges
    @@ -17,6 +17,8 @@
     +    my $self = shift;
     +    return qr{
     +        now
    ++        | created
    ++        | last \ ? updated
     +        | cf\. (?: \{ .*? \} | \S+ )
     +    }xi;
     +}
    @@ -35,6 +37,12 @@
     +    if (lc($field) eq 'now') {
     +        $date->Set(Format => 'unix', Value => time);
     +    }
    ++    elsif (lc($field) eq 'created') {
    ++        $date = $self->CreatedObj;
    ++    }
    ++    elsif ($field =~ /^last ?updated$/i) {
    ++        $date = $self->LastUpdatedObj;
    ++    }
     +    elsif ($field =~ m{^ cf\. (?: \{ (.*?) \} | (\S+) ) $}xi) {
     +        my $name = $1 || $2;
     +        my $value = $self->FirstCustomFieldValue($name);
    @@ -44,7 +52,7 @@
     +            return;
     +        }
     +
    -+        $date->Set(Format => 'unknown', Value => $value);
    ++        $date->Set(Format => 'unknown', Value => $value, Timezone => 'UTC');
     +    }
     +    else {
     +        RT->Logger->error("Unable to parse '$field' as a field name in CustomDateRanges '$range_name'");
 2: 620ea2a1e !  2: 01907da45 RT::Ticket support for CustomDateRanges
    @@ -9,22 +9,17 @@
                 !RT->Config->Get('HideTimeFieldsFromUnprivilegedUsers');
      }
      
    --1;
     +sub _DateForCustomDateRangeField {
     +    my $self  = shift;
     +    my $orig  = shift;
     +    my $field = lc($orig);
     +
    -+       if ($field eq 'created')  { return $self->CreatedObj }
    -+    elsif ($field eq 'starts')   { return $self->StartsObj }
    ++    if ($field eq 'starts')   { return $self->StartsObj }
     +    elsif ($field eq 'started')  { return $self->StartedObj }
     +    elsif ($field eq 'due')      { return $self->DueObj }
     +    elsif ($field eq 'resolved') { return $self->ResolvedObj }
     +    elsif ($field =~ /^(?:told|last ?contact)$/i) {
     +        return $self->ToldObj;
    -+    }
    -+    elsif ($field =~ /^last ?updated$/i) {
    -+        return $self->LastUpdatedObj;
     +    }
     +    else {
     +        return $self->SUPER::_DateForCustomDateRangeField($orig, @_);
    @@ -34,17 +29,16 @@
     +sub _CustomDateRangeFieldParser {
     +    my $self = shift;
     +    return $self->SUPER::_CustomDateRangeFieldParser . '|' . qr{
    -+          created
    -+        | starts
    ++        starts
     +        | started
    -+        | last \ ? updated
     +        | told
     +        | last \ ? contact
     +        | due
     +        | resolved
     +    }xi;
     +}
    ++
    + sub Table {'Tickets'}
      
    - =head1 AUTHOR
    - 
    + =head2 id
     
 3: 31d70171d < --:  ------- RT::Asset support for CustomDateRanges
 4: 0bb4ac738 =  3: fb40485cf Add RT::Ticket CustomDateRanges to query builder
 5: 4f200c560 =  4: 8de03df87 Add Asset ColumnMap entries for CustomDateRanges
 6: 73e39a567 =  5: df406a580 Add config validation for CustomDateRanges
 7: f6a01b4e1 !  6: 590c7dbd5 RT_Config doc for CustomDateRanges
    @@ -22,7 +22,7 @@
     +        'RT::Ticket' => {
     +            'Resolution Time' => 'Resolved - Created',
     +
    -+            'Downtime' => 'CF.{First Alert} - CF.Recovered',
    ++            'Downtime' => 'CF.Recovered - CF.{First Alert}',
     +
     +            'Time To Beta' => {
     +                value => 'CF.Beta - now',
 8: c3189cdb6 =  7: 3e4bedbd2 Switch customization doc from date range to message count
 9: 8326b0ac8 =  8: 2ce3c1f40 Remove "# loc" and description from example
10: fd018fe2e =  9: b6822facb Add tests for CustomDateRanges