Children, dependencies, etc

For some reason this didnt seem to post

I may be missing something, but lets say I want to create dependencies, and
child tickets under a parent… Fairly simple task to do, but what I am
wondering about is that I seem to be able to resolve a parent ticket while
children are still open or even a ticket when it has open dependencies. Is
there a way (other than user training) to keep master tickets from being
closed until all children are either closed or unlinked?

Thanks

– Kevin Welch

My apologies for outlook and its annoying way of all replys being RTF or
HTML.

– Kevin-----Original Message-----
From: rt-users-admin@lists.fsck.com [mailto:rt-users-admin@lists.fsck.com]On
Behalf Of Kevin Welch
Sent: Tuesday, April 30, 2002 8:33 AM
To: 'rt-users@lists.fsck.com’
Subject: [rt-users] Children, dependencies, etc.

For some reason this didnt seem to post

I may be missing something, but lets say I want to create dependencies, and
child tickets under a parent… Fairly simple task to do, but what I am
wondering about is that I seem to be able to resolve a parent ticket while
children are still open or even a ticket when it has open dependencies. Is
there a way (other than user training) to keep master tickets from being
closed until all children are either closed or unlinked?

Thanks

– Kevin Welch

I may be missing something, but lets say I want to create dependencies, and
child tickets under a parent… Fairly simple task to do, but what I am
wondering about is that I seem to be able to resolve a parent ticket while
children are still open or even a ticket when it has open dependencies. Is
there a way (other than user training) to keep master tickets from being
closed until all children are either closed or unlinked?

Currently, RT has the concept of such dependencies, but not all of the
functionality behind said dependencies as yet.

Regards,

                         Bruce Campbell                            RIPE
               Systems/Network Engineer                             NCC
             www.ripe.net - PGP562C8B1B                      Operations

a message of 26 lines which said:

children are still open or even a ticket when it has open dependencies. Is
there a way (other than user training) to keep master tickets from being
closed until all children are either closed or unlinked?

Currently, RT has the concept of such dependencies, but not all of the
functionality behind said dependencies as yet.

I’ve noticed the same behavior than Kevin and the workaround I use is
a program run by cron to find out tickets closed (“base”) while they
depend on open tickets (“targets”). You can even reopen them or raise
the priority of the target.

SELECT t_base.id,t_base.subject,l.type,t_target.id,t_target.subject
FROM links l,tickets t_target, tickets t_base
WHERE l.type = ‘DependsOn’ AND t_target.id = l.localtarget AND
t_base.status = ‘resolved’ AND t_base.id = l.localbase AND
(t_target.status = ‘open’ OR t_target.status = ‘new’);