“Matt Hanley” MHANLEY@cxtec.com writes:
I am considering purchasing the RT Essentials book. Since there’s no
table of contents on-line, and the example chapter is on installing RT,
it’s tough to get a feel for how in-depth the book is.
Can anyone share any insights?
I got my copy this morning and I’m currently browsing through it.
It seems very promising, with thorough chapters on writing scrips and
the architecture of RT.
On the downside, the book could use some proofreading and editing.
There are quite a few cut’n’paste errors, and the writing is not
always crystal clear. For example, the second and third paragraphs of
the section “Associating Related Tickets” on page 42 are rather
[About Depends On/Depended On By] You can create this relationship
from the other direction as well: on the Links form for the original
ticket you can enter the new ticket’s number in the Depends On
field. Once this relationship is established, the parent ticket
cannot be resolved until the child ticket is resolved. A ticket can
have multiple parents and multiple children, which can be used to
create arbitrarily complex and interdependent workflows.
The Depends On/Depended On By relationships are similar to the
parent and child relationships. The practical difference is that RT
doesn’t enforce the relationships. With parent/child relationships,
the parent ticket cannot be resolved until all the child tickets are
resolved, but with Depends On/Depended On By relationships, either
ticket can be resolved without the other.
OK, I’m rather sleepy today, but I’m having trouble following this…
Leif Nixon - Systems expert
National Supercomputer Centre - Linkoping University