[rt-users] Anyone know the status of RT-ProjectManager?

[Roderick A. Anderson]

This looks very promising for my needs at least.  Our work flow is 
pretty structured and would rarely need changes in child tickets.

Is your code looking generalized or is it tied closely to your process(es)?


Rod
-- 
Chuck Boeheim wrote:
> We're just starting to model our installation workflow in RT, in
> the following way.  The Installation queue has some custom fields
> attached to tickets to indicate tasks that are typically
> involved in the installation of new equipment:
>   OrderStatus
>   Power
>   Network
>   Rack
>   DNS
>   OSInstall
> These are drop-down lists with possible values of (none),
> Required, and Completed.  Setting one or more fields to
> Required creates a child ticket for that subtask, using
> a template that puts the child ticket in the correct
> queue, assigned to the correct person for the subtask
> (with adminCC to the person's backup).  When the subtask
> is resolved, the corresponding custom field in the parent
> ticket is changed to Completed, so the parent ticket
> has a summary of the subtask status.
> 
> We're playing with attaching pdfs of the purchase order
> to the ticket, and links to the purchase database, but
> this is not automated yet.
> 
> We're still refining the process and stepping through the
> first few installs using it to see what needs to be changed,
> so I'm not ready to post any code just yet, but we can do
> that when it settles down in a bit.
> 
> One question is how much this intersects with the capabilities
> of RT-ProjectManager, and what we would have done differently
> if that were available?  We are lacking a good way to
> get a look at the whole project without opening each
> child ticket, and a way to automatically update child
> tickets if there are changes that affect them (e.g.,
> if the user increases the size of the order, the
> child tickets for power planning and rack space should
> be updated with the new requirements).
> 
> Chuck Boeheim
> boeheim at slac.stanford.edu
> 

<snip />