It sounds like the SLA extension is performing its work after all scrips run instead of before TransactionBatch scrips.
I would be inclined to suggest that this is an SLA bug/oversight, as its current design doesn't seem to permit proper execution of TransactionBatch scrips and its documentation doesn't provide a workaround. Please consider describing this situation in a bug report so that an "official" response can be recorded: http://rt.cpan.org/Public/Dist/Display.html?Name=RT-Extension-SLA On 18/09/2014 8:28 pm, "andriusk" <[email protected]> wrote: > > > The last two transactions is because of SLA was changed and the due and > priority must be changed accordingly. > > How can I get my scrip run after these two last transactions, because now > it > is ran first (Found 1 scrips for TransactionBatch stage with applicable > type(s) Status,Set,SetWatcher,CustomField). This is a real headache form > me... > > > > -- > View this message in context: > http://requesttracker.8502.n7.nabble.com/Catch-all-ticket-changes-in-one-scrip-tp58372p58567.html > Sent from the Request Tracker - User mailing list archive at Nabble.com. > -- > RT Training November 4 & 5 Los Angeles > http://bestpractical.com/training >
-- RT Training November 4 & 5 Los Angeles http://bestpractical.com/training
