Auto-escalation AKA time-triggered scrips


#1

I was thinking about a subject of auto-escalation for a given ticket, and
essentially it seems to be its about having a scrip be called on a event
that’s determined by time. (Such as, if the ticket has been in a given
condition for X hours, move it to a given quote, or some such).

So, apparently, to implement such, there’s a need for rtd, a daemon which
would scan all queues every minute, see if a scrip condition has been met,
and execute the scrip.

I’m willing to implement it as described above, if it makes sense :slight_smile:

-alex


#2

I’ve actually been looking at what it would take to build an rtcron system
for a client. I might well have something to show within a few weeks.

FWIW, the scan every ticket every minute method just won’t scale past
a few thousand tickets. But there are ways to get what we want :slight_smile:

    -jOn Wed, May 30, 2001 at 04:06:19PM -0400, Alex Pilosov wrote:

I was thinking about a subject of auto-escalation for a given ticket, and
essentially it seems to be its about having a scrip be called on a event
that’s determined by time. (Such as, if the ticket has been in a given
condition for X hours, move it to a given quote, or some such).

So, apparently, to implement such, there’s a need for rtd, a daemon which
would scan all queues every minute, see if a scrip condition has been met,
and execute the scrip.

I’m willing to implement it as described above, if it makes sense :slight_smile:

-alex


Rt-devel mailing list
Rt-devel@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-devel

jesse reed vincent – root@eruditorum.orgjesse@fsck.com
70EBAC90: 2A07 FC22 7DB4 42C1 9D71 0108 41A3 3FB3 70EB AC90

As I sit here alone looking at green text on a laptop in a mostly bare room listening
to loud music wearing all black, I realize that that it is much less cool in real life :slight_smile:
–Richard Tibbetts


#3

Well, I’m not that silly. :slight_smile:

It’d be a fancy query ran every minute. (Or a set of queries, one per
scrip). But I guess I’ll wait for you. Thanks!

Oh…and that mailgate would be awfully nice to have :P)

-alexOn Wed, 30 May 2001, Jesse wrote:

I’ve actually been looking at what it would take to build an rtcron system
for a client. I might well have something to show within a few weeks.

FWIW, the scan every ticket every minute method just won’t scale past
a few thousand tickets. But there are ways to get what we want :slight_smile:

    -j

On Wed, May 30, 2001 at 04:06:19PM -0400, Alex Pilosov wrote:

I was thinking about a subject of auto-escalation for a given ticket, and
essentially it seems to be its about having a scrip be called on a event
that’s determined by time. (Such as, if the ticket has been in a given
condition for X hours, move it to a given quote, or some such).

So, apparently, to implement such, there’s a need for rtd, a daemon which
would scan all queues every minute, see if a scrip condition has been met,
and execute the scrip.

I’m willing to implement it as described above, if it makes sense :slight_smile:

-alex


Rt-devel mailing list
Rt-devel@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-devel