[rt-devel] Ticket Dependencies within RT

[Jesse Vincent]

I'd definitely like to see code for this. However, I'd love to see this code
in something like a Scrip.. But to do that, we're going to need a new callback
so that scrips can be run _before_ the action is committed and some way to 
signal RT and the user that the action that's going on can't continue.

	Does that make sense? Comments? Ideas?

	-jesse

On Thu, Aug 30, 2001 at 05:14:44AM -0500, david.sarno at yale.edu wrote:
> I've been fooling with the dependencies features, and they seem to work 
> great.  However, it seems that the dependency links don't actually DO 
> anything except sit there passively.  You can close dependant tickets  
> while the tickets they depend on are still open (or new), without so 
> much as a peep from RT.  
> 
> It might be useful to have an option to warn users when they try to 
> resolve a ticket that has unresolved or unopen dependencies.  Otherwise 
> you could easily imagine scenarios where things get done in the wrong 
> order.  If you've ever written a make implementation, you know the order 
> in which dependencies are addressed is critical.  Same with tasks in an 
> IT office, supermarket, church or even a military installation (many of 
> which bases might well consider RT an inexpensive alternative now that 
> all the money's going to The Antimissilemissle Missile Project).
> 
> I would be happy to look into adding the code for this.  I would also be 
> happy to hear that I'm completely wrong about either the idea or the 
> fact that it hasn't already been implemented (and I just couldn't figure 
> it out).
> 
> Thanks,
> 
> Dave
> 
> 
> 
> _______________________________________________
> rt-devel mailing list
> rt-devel at lists.fsck.com
> http://lists.fsck.com/mailman/listinfo/rt-devel
> 

-- 
http://www.bestpractical.com/products/rt  -- Trouble Ticketing. Free.