[Rt-commit] rt branch, 4.4/automating-rt-multiple-actions-docs, repushed
Craig Kaiser
craig at bestpractical.com
Thu Jul 5 16:59:46 EDT 2018
The branch 4.4/automating-rt-multiple-actions-docs was deleted and repushed:
was db707e681452e17835f31e580501545603e3a27a
now 9971eeed15978f1e9caf1a0ef51947628cbc13c7
1: c229a9233 ! 1: 9971eeed1 Add documentation for automating-rt, using rt-crontool with multiple --action parameters.
@@ -1,6 +1,6 @@
-Author: craig <craig at bestpractical.com>
+Author: Craig Kaiser <craig at bestpractical.com>
- Adding documentatiion for automating-rt, using rt-crontool with multiple --action parameters.
+ Add documentation for automating-rt, using rt-crontool with multiple --action parameters.
diff --git a/docs/automating_rt.pod b/docs/automating_rt.pod
--- a/docs/automating_rt.pod
@@ -9,7 +9,7 @@
for RT actions. Since this class doesn't perform any action itself, this
command will just output the results of the TicketSQL search.
-+=head2 Multiple --Action parameters
++=head2 Multiple --Action Parameters
+
+ /opt/rt4/bin/rt-crontool \
+ --search RT::Search::FromSQL \
@@ -20,10 +20,10 @@
+ --transaction last \
+ --template 'Stalled ticket resolved' \
+
-+rt-crontool can also take more than one --action parameter to perform multiple steps are a time. In the example above
-+two actions are completed first it checks for any tickets with a "stalled" status and then marks them as resolved.
-+As well as notifies the Requestors on the ticket of the change.p
++rt-crontool can take more than one --action parameter to perform multiple steps at a time. In the example above
++two actions are completed, first the SetStatus action then the Notify action.
++
++
=head1 Auto-resolve Aged Tickets
You can auto-set status based on any criteria you can define in
-
2: db707e681 < -: ------- Adding documentatiion for automating-rt, using rt-crontool with multiple --action parameters.
More information about the rt-commit
mailing list