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:
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).
email@example.comOn Mar 29, 2006, at 9:38 AM, Roderick A. Anderson wrote:
Jesse Vincent wrote:
On Tue, Mar 28, 2006 at 04:09:32PM -0700, Jason Forbes wrote:
So, is it usable? Or should I look for something else? We can
off-list if you’d prefer. Jason
That particular tool isn’t useful these days, though plenty of
regular RT for project management. I’d be thrilled to see or work on
Gantt charts, PERT charts and the rest
I’m researching this functionality ( started yesterday after over a
month of letting messages build up in the folder ). I’m not sure
if it is PM I’m looking for as much as a method to do work flow
We have several complex ( and reoccurring ) projects with several
dependencies and dependencies of dependencies. These happen on a
regular basis ( monthly, bi-monthly ) and sometimes irregularly.
I’m looking for a way to automagically create all the tickets and
sub tickets then probably edit each correcting due date and the
assigned to for each of the projects.
Charting is OK but less necessary.
What would it cost to whip RT-ProjectManager into shape?
Community help: http://wiki.bestpractical.com
Commercial support: firstname.lastname@example.org
Discover RT’s hidden secrets with RT Essentials from O’Reilly
Media. Buy a copy at http://rtbook.bestpractical.com
We’re hiring! Come hack Perl for Best Practical: http://