[Bps-public-commit] r11264 - experiments/rt-rules
jesse at bestpractical.com
jesse at bestpractical.com
Sat Mar 29 17:30:37 EDT 2008
Author: jesse
Date: Sat Mar 29 17:30:37 2008
New Revision: 11264
Modified:
experiments/rt-rules/README
Log:
more notes
Modified: experiments/rt-rules/README
==============================================================================
--- experiments/rt-rules/README (original)
+++ experiments/rt-rules/README Sat Mar 29 17:30:37 2008
@@ -30,6 +30,8 @@
=head1 Desired features
+=head2 allow users to "program" RT to behave differently with little or no programming background.
+
=head2 Ability to mark certain rules to run asynchronously
Or is it that all rules that run "after" an action automatically run async?
@@ -46,6 +48,12 @@
=head2 It should be possible for a user to define rules that can be manually triggered
+=head2 Users should be able to define 'personal' mailing rules.
+
+=head2 Group administrators should be able to define 'group-wide' mailing rules.
+
+=head2 Queue admins should be able to define role-based mailing rules
+
=head1 Non-goals (What's out of scope)
@@ -60,4 +68,15 @@
=back
+=head1 Sample rules
+
+
+* When a ticket is created by someone whose email address matches 'foo.com', send them back a special autoreply, assign the ticket to susan and bump it's priority by 25.
+
+* When a ticket is created, notify the queue's adminccs with the message in the template "message creation"
+
+* If I try to create a ticket in the 'Ops' Queue with an owner of nobody, reject the create
+
+
+
=cut
More information about the Bps-public-commit
mailing list