[rt-users] Fw: parent/child tickets

[Matthew Watson]

Hi,

 I don't believe any actions actually happen on with parent/child
relationships, it is used (at the moment) purely to describe the
Relationship between tickets, although you could well setup your
own actions without too much difficulty.

Regards,
Matt

> -----Original Message-----
> From: rt-users-bounces at lists.bestpractical.com [mailto:rt-users-
> bounces at lists.bestpractical.com] On Behalf Of Raed El - Hames
> Sent: Friday, April 01, 2005 7:28 AM
> To: RT Mailing List
> Cc: rfh at pipex.net
> Subject: [rt-users] Fw: parent/child tickets
> 
> > Hi there;
> >
> > Can someone help me understand the parent/child tickets
relationship,
> from
> > my understanding in reading
> >
> http://svn.bestpractical.com/cgi-
>
bin/index.cgi/bps/checkout/rt/branches/3.2-RELEASE/docs/design_docs/link
-
> definitions.txt?rev=1225
> > updating a parent should update the child (I am assuming that the
> Memberof
> > discussed in the above link means Parent/child), now I am not sure
if
> there
> > is something broken in my installation but whenever I update the
parent
> this
> > update is not propagated to the  children of this ticket .. Any help
> will
> be
> > greately appreciated !!
> > I am running RT3.2, on Gentoo, searchbuilder 1.16, perl,Mysql ..I
think
> this
> > should cover it for this query!!
> >
> > Roy
> >
> 
> _______________________________________________
> http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
> 
> RT Administrator and Developer training is coming to your town soon!
> (Boston, San Francisco, Austin, Sydney) Contact
training at bestpractical.com
> for details.
> 
> Be sure to check out the RT Wiki at http://wiki.bestpractical.com

This email and any files transmitted with it are confidential and intended solely for the 
use of the individual or entity to whom they are addressed. Please notify the sender 
immediately by email if you have received this email by mistake and delete this email 
from your system. Please note that any views or opinions presented in this email are solely
 those of the author and do not necessarily represent those of the organisation. 
Finally, the recipient should check this email and any attachments for the presence of 
viruses. The organisation accepts no liability for any damage caused by any virus 
transmitted by this email.