[rt-users] using approvals in RT3.0

[THAUVIN Blaise (Dir. Informatique)]

1) Create a global (or not) template. This template will be used to create
"approval tickets".
Name it as you want, and but the text between the "--------" below in
"content" section.
----------------------------
===Create-Ticket: codereview
Subject: Code review for {$Tickets{'TOP'}->Subject}
Queue: Approbations
Type: Approval
Depended-On-By: {$Tickets{'TOP'}->Id}
Content: Someone has created a ticket. you should review and approve it, so
they can finish their work
ENDOFCONTENT
--------------------------

When fired, this template creates a ticket in queue "approbations" (change
it for your queue) of type "approval" and links it to the parent ticket.



2) Create a scrip in your main queue (in order to avoid loops in tickets and
approval creation, they should not reside in the same queue). Parameters are
:
- Condition : On creation
- Action : Create ticket
- Model : using template above.



3) Now, if you create a new ticket in your main queue, a children ticket of
type approval will be automatically created in the approval queue. you'll
see it by clicking on the "approbation" link. You can approve, reject, or do
nothing on the ticket.

This is a very basic example just to give you a start. You can find more
details in Jesse's documentation on which variables can be used in ticket
creation to get some more useful behaviour.


Blaise.




On Tue, Mar 25, 2003 at 10:53:13AM -0500, Chris Hardie wrote:
> Can anyone offer any pointers (okay, step-by-step instructions would be
> nice too :) for getting approvals working?

(Not much a pointer but a heads-up)

I'm currently busily implementing an alternative UI set for RT,
and just finished the Workflow editing part, which saves the
admin from hand-editing the Create-Ticket templates; it also sets
up the CreateTicket actions automagically.

A screenshot is available at http://aut.dyndns.org/tmp/workflow.jpg
and the code lives in http://p4.elixus.org/depot/RT/104/.  I'll be
de-chinesify the UI in the next week and hopefully merge the
functionality back to the 'canonical' UI (if time allows), which
will then be available at our development branch snapshot:

    http://p4.elixus.org/snap/rt.tar.gz

Note that this is a branch, not a fork -- the tree merges from Jesse's
main tree at every point release, and merges upstream periodically.

Thanks,
/Autrijus/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20030326/48e50922/attachment.htm>