Relationships: What Do They Mean?

Howdy!

I’d like to check my understanding of relationships in RT tickets.

Parent/Child would seem to indicate that a parent issue revealed one or
several smaller issues. Perhaps the parent issue was divided among
several children and closed in favor of them; perhaps it’s an umbrella
for tracking a big project.

Requisite/Dependent (“Depended on by”/“Depends on”) is more clear; you
can’t finish and close the dependent until the requisite is done.

Reference (“Refers to”/“Referred to by”) is a peer relationship,
primarily useful for navigation and relation of interesting tickets.

Any comments on these descriptions is welcome; I’d also love to hear how
folks use these.

Thanks!

–j
Jim Meyer, Geek At Large purp@wildbrain.com

From: Jim Meyer [mailto:purp@wildbrain.com]

I’d like to check my understanding of relationships in RT tickets.

Parent/Child would seem to indicate that a parent issue
revealed one or
several smaller issues. Perhaps the parent issue was divided among
several children and closed in favor of them; perhaps it’s an umbrella
for tracking a big project.

I’ve been using it here as a sort of kludgy way to set up hierarchical
relationships between a task and its subtasks.

I’ll have one master ticket that is really just a placeholder, containing
something like a definition of the task, and then several tickets set up as
children, each one enumerating one of the major steps in accomplishing the
main task. I’ve ended up nesting several levels deep. Kind of a poor man’s
MS Project, and probably not the intended purpose, but it works for me. :slight_smile:

Kendric Beachey