The errata list is a list of errors and their corrections that were found after the product was released.
The following errata were submitted by our customers and have not yet been approved or disproved by the author or editor. They solely represent the opinion of the customer.
Color Key: Serious technical mistake Minor technical mistake Language or formatting error Typo Question Note Update
| Version |
Location |
Description |
Submitted by |
Date submitted |
| Printed |
Page 42
Second and third paragraphs |
The descriptions of Depends On and Depended On By, and of Parents
and Children, is confusing. Paragraph one introduces Depends On and
Depended On By. Paragraph two continues talking about those.
The second sentence in that paragraph talks about the "parent"
and "child" tickets (lower case), which is a bit confusing when
there are also "Parent" and "Children" fields which are not the
parent and child we're talking about now. The key point in this
paragraph is that a "Depends On" cannot be closed until all its
"Depended On By" relatives are closed.
The first sentence of the third paragraph starts off as though we are
only just now talking about the Depends relationships in contrast to
the "parent and child" (lower case). But we were just talking about
Depends in the previous paragraph. It goes on to say that the
relationship is not enforced for Depends, but the previous paragraph
said it was enforced for Depends.
Nowhere are the "Parents" and "Children" (with capitals, matching the
field names) described.
Experimentally, it seems that the relationship is enforced for
Depends, but not enforced for Parent/Children, which is what one
might expect based on the names.
So it looks to me like the second paragraph should say
something like this:
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 Depends On ticket cannot be
resolved until the Depended On By tickets are resolved.
The third paragraph should say something like this:
The Parents/Children relationships are similar to the Depends
On/Depended On By relationships. The practical difference is
that RT doesn't enforce the relationships. With Depends
relationships, the parent ticket cannot be resolved until all
the child tickets are resolved, but with Parent/Children
relationships, either ticket can be resolved without the other.
And then the last sentence from the original second paragraph
could finish things up as a new fourth paragraph, since it
is true for both the Parent/Children and the Depends:
A ticket can have multiple Parents/Children and/or multiple
Depends On/Depended On By, which can be used to create
arbitrarily complex and interdependent workflows.
Note from the Author or Editor:
This entire section needs to be rewritten. -RS |
Anonymous |
|