Adding field relationships

Add field relationships to restrict values users can select in a child field based on the value selected in a parent field. For example, you can add a field relationship with Product as the parent field and Version Found as the child field to make sure users can only select a valid version number an issue was found in based on the corresponding product.

Keep the following in mind:

  • A parent field can have one or more child field relationships. A child field can only have one parent. A child field can also be the parent of another field.
  • User fields cannot be set as parent or child fields.
  • Workflow event fields can only be parents to other fields in the same workflow event.

1.Choose Tools > Administration > Field Relationships.

The Field Relationship Selection dialog box opens.

2. Select an Item type. The fields displayed depend on the selected type.

3. Click Add.

The Setup Parent-Child Relationship dialog box opens.

4. Select a Parent field. When users add or edit items, the value selected in this field restricts the values in the child field.

The list does not include pop-up menu fields that support multiple selection because they cannot be parent fields.

5. Select a Child field. When users add or edit items, the values available in this field depend on the value selected in the parent field.

Fields already set as a parent or grandparent for the selected Parent field are excluded from the list to prevent circular references. For example, if Field A is the parent to Field B in a relationship and Field B is the parent to Field C in another, you cannot select Field A or Field B to be a child of Field C. Fields already set as the child field in a relationship are also excluded because a child field can only have one parent field.

6. Click OK.

The Setup Field Relationships dialog box opens.

7. Select or clear child field values for each value in the parent list.

8. Click OK when you finish.

You return to the Field Relationship Selection dialog box.

9. Click OK to save the changes.

Tip:  If a project uses default values, the child field’s default value may be invalid, depending on the parent field’s default value. The default value can still be used.

Hidden fields can cause unintended changes. If a parent field is changed, the child field may be changed to <not set> depending on project options. In addition, changes cannot be saved if the child field is required.