Thanks for looking it up. I guess we'll have to set it to a lower value, or maybe leave the Due field empty for our problems / changes.
-- Bart 2011/9/26 Thomas Sibley <[email protected]> > On 09/26/2011 06:09 AM, Bart wrote: > > I'm kinda stubbed since 480 comes down to 27000 minutes, I don't know if > > that's too much and if so what the maximum amount could be (16000 > > something?), if there's a maximum then we'd want to use that instead. > > > > In case your wondering, 480 is about 3 months. We want to use that > > setting for e.g. problems or long running changes. > > > > So, does anyone know if there's a limit to the height of the SLA > > plugin's resolve time in BusinessMinutes? > > From the add_seconds method in Business::Hours: > > # the maximum time after which we stop searching for business hours > my $MAXTIME = ( 30 * 24 * 60 * 60 ); # 30 days > > and later: > > if ( $end >= $start + $MAXTIME ) { > return -1; > } > > I believe this arbitrary limit is to prevent endless loops with > pathological configurations and bound the search time. It's come up > before on this mailing list, and I know some folks have simply patched > the module to use a higher $MAXTIME. > > Thomas > -------- > RT Training Sessions (http://bestpractical.com/services/training.html) > * Chicago, IL, USA September 26 & 27, 2011 > * San Francisco, CA, USA October 18 & 19, 2011 > * Washington DC, USA October 31 & November 1, 2011 > * Melbourne VIC, Australia November 28 & 29, 2011 > * Barcelona, Spain November 28 & 29, 2011 >
-------- RT Training Sessions (http://bestpractical.com/services/training.html) * Chicago, IL, USA September 26 & 27, 2011 * San Francisco, CA, USA October 18 & 19, 2011 * Washington DC, USA October 31 & November 1, 2011 * Melbourne VIC, Australia November 28 & 29, 2011 * Barcelona, Spain November 28 & 29, 2011
