Richard,
Actually, I've NEVER been able to resolve a parent ticket without all
the children tickets being resolved first. Because of the way the LINKS
table works, I can have a child ticket ALSO be a DependedOnBy ticket
as well, although I'm not sure that is required. I even remember
Hi all,
what is the conceptual difference between Parent/Child and Depends on/
Depended on by? To me, they mean essentially the same and I can't come
up with a use case where both would be used simultaneously or even just
differently.
If there is no real difference, wouldn't it make sense to
On Mon, 22 Sep 2008 07:10:22 -0400, Richard Hartmann
[EMAIL PROTECTED] wrote:
Hi all,
what is the conceptual difference between Parent/Child and Depends on/
Depended on by? To me, they mean essentially the same and I can't come
up with a use case where both would be used simultaneously or
On Mon, Sep 22, 2008 at 15:03, Stephen Turner [EMAIL PROTECTED] wrote:
Parent/child simply describes a relationship between tickets (children
belong to parent). Depends on enforces a rule - the depended on ticket must
be resolved before its dependent tickets can be resolved.
So basically,
On Mon, 22 Sep 2008 10:35:01 -0400, Richard Hartmann
[EMAIL PROTECTED] wrote:
So basically, parent/child sit between the strong Depend and the weak
Refer. Not sure if that is useful in any application, but I now know
that I don't need it for my workflows.
Thanks :)
Richard
I think
Richard,
There is also another difference. In the LINKS table, the TYPE of
link maintained for a ticket is also different. In a situation where
there is a Parent/Child relationship, the type is defined as MembersOf
and if it is a DependsOn relationship, then the type is defined as
Richard,
We use the Parent/Child and DependsOn relationships a great deal and
this is how we do it. Whenever we have a ticket that in and of itself
causes other work to be done within the SAME support group for the same
queue, we make those tickets Children tickets of the
