"On Reply" conditions

The workflow I’m looking to emulate using RT causes emails from customers to
our support address to either create a new case or change an existing case
to an ‘open’ state.

This works pretty well with the default templates and scrips in RT 3.0.10.

The missing bit of the puzzle is that replies from support (which cc the
support address) should change the case state to a ‘pending’ state.

The equivalent to this ‘pending’ state seems to be RT’s ‘stalled’ state,
which I can live with. (Is it easy to extend the ticket states?)

However where I’m stuck is that the draft RT3 manual describes some
conditions etc, but these don’t appear to exist in RT. Specifically, the “On
Reply” condition would seem to be the one I’m looking for.

I had a quick look at creating my own conditions, but didn’t find the right
bit of POD to tell me how to get email addresses out of transactions.

Should I be looking at writing my own conditions, or is the "On reply"
condition actually around somewhere that I simply can’t see?

Cheers,

Chris

Chris Ridd wrote:

The workflow I’m looking to emulate using RT causes emails from customers to
our support address to either create a new case or change an existing case
to an ‘open’ state.

This works pretty well with the default templates and scrips in RT 3.0.10.

The missing bit of the puzzle is that replies from support (which cc the
support address) should change the case state to a ‘pending’ state.

The equivalent to this ‘pending’ state seems to be RT’s ‘stalled’ state,
which I can live with. (Is it easy to extend the ticket states?)
Nop. Not easy.

However where I’m stuck is that the draft RT3 manual describes some
conditions etc, but these don’t appear to exist in RT. Specifically, the “On
Reply” condition would seem to be the one I’m looking for.

I had a quick look at creating my own conditions, but didn’t find the right
bit of POD to tell me how to get email addresses out of transactions.

Should I be looking at writing my own conditions, or is the “On reply”
condition actually around somewhere that I simply can’t see?
On Correspond. Manual should be fixed.

I think “On Reply” is what RT2 called it, “On Correspond” is RT3. They seem to
be synonymous in function. Or at least the closest match.

The workflow I’m looking to emulate using RT causes emails from customers to
our support address to either create a new case or change an existing case
to an ‘open’ state.

This works pretty well with the default templates and scrips in RT 3.0.10.

The missing bit of the puzzle is that replies from support (which cc the
support address) should change the case state to a ‘pending’ state.

The equivalent to this ‘pending’ state seems to be RT’s ‘stalled’ state,
which I can live with. (Is it easy to extend the ticket states?)

However where I’m stuck is that the draft RT3 manual describes some
conditions etc, but these don’t appear to exist in RT. Specifically, the “On
Reply” condition would seem to be the one I’m looking for.

I had a quick look at creating my own conditions, but didn’t find the right
bit of POD to tell me how to get email addresses out of transactions.

Should I be looking at writing my own conditions, or is the “On reply”
condition actually around somewhere that I simply can’t see?

Cheers,

Chris


The rt-users Archives

RT Training is coming to town this summer!
Sign up for an RT Developer/Administrator class in DC, LA or Frankfurt by emailing training@bestpractical.com

For more details, check out http://www.bestpractical.com/services/training.html

The RT Wiki lives at http://wiki.bestpractical.com Read! Join! Contribute!

Chris Ridd wrote:

The equivalent to this ‘pending’ state seems to be RT’s ‘stalled’ state,
which I can live with. (Is it easy to extend the ticket states?)
Nop. Not easy.

OK.

Should I be looking at writing my own conditions, or is the “On reply”
condition actually around somewhere that I simply can’t see?
On Correspond. Manual should be fixed.

Ah, thanks. I’ll log a bug.

Cheers,

Chris