Field dependencies allow us to link source field values to target field values. In other words, the values proposed to a final user for a field will depend upon the value selected for another field.
As an example, if you define a field Operating System(Linux, MacOS X, MS Windows, NetBSD) and a field Version(2.0, 2.1, 2.2, 2.4, 2.6, 3.0, 10.1, 10.2, 10.3, 10.4 (Tiger), NT, 2000, XP), you can define dependencies in the tracker administration interface:
First, select the source field “Operating System” then the target field “Version”.
To create dependencies between each “Operating System” values and the corresponding versions, you just have to check the corresponding box in the matrix.
First, you select a source field.
The cyclic dependencies are forbidden (Field 1 => Field 2 => … => Field 1),
A field can depend upon only one field,
If a field is not the target of a dependency, then it will propose all its values. On the opposite, it will propose only those which satisfy the dependencies.