The "Dependencies" field is a way to identify what other work must be done (all, or in part) before a work request can be completed. Dependencies are usually ST serial numbers, although there are a few other forms of reference that can be used. They're typically only needed for large projects.
Preceding the dependency list display is one line for each dependency, as well as for each dependency of those, displaying the entire dependency tree. Nothing is displayed for items that don't exist.
Lines are of the form:
<serial number> <status> <indent> <subject>where:
- <serial number>
- is a link to the corresponding item;
- is the item completion status, shown as empty if the item isn't completed;
- is indentation depicting the distance from the starting item; and thus is indented from the previous line if it's a dependency of the previous item;
- is the subject of the item.
When a subtree is found that has already been displayed, the children of the tree aren't displayed. Instead, the subject of the top of each duplicated tree has one of the following appended:
[1 child skipped]
[number_skipped children skipped]
Only the first iteration of a loop is displayed.
A simple example might be of the form:
and a slightly more complicated example would be:
NNNNN1 a starting point NNNNN2 done needed for NNNNN1 NNNNN3 done needed for NNNNN2
NNNNN1 a starting point NNNNN2 done needed for NNNNN1 NNNNN3 done needed for NNNNN1 NNNNN4 done needed for NNNNN3