Customizing fields

To capture all necessary information about items and use your team's terminology, you can change properties of existing fields in the project or create custom fields so users can provide additional information. You can:

  • Use field layouts to organize fields in groups in the Add, Edit, and View item windows in the Helix ALM desktop client and Add, Edit, and View item pages in the web client. Field layouts can help support different users needing different fields based on their team or function, or help capture the most important information about each requirement type. See Configuring field layouts.
  • Rename field labels to use different terminology. For example, you may want to use 'defects' instead of 'issues'. See Renaming field labels.
  • Make fields required to ensure information is entered or selected in a field before saving an item. See Defining required fields and default values.
  • Specify the default value displayed in a field. For example, you may want a requirement Description field to display instructions about information the description should include. See Defining required fields and default values.
  • Configure parent/child field relationships that restrict the values available in lists based on the value selected in another list defined as the parent. For example, you may want to limit the values in the Component field based on the value selected in the Product field. See Configuring field relationships.
  • Add, edit, and delete list field values. You can also change the order of values in a list. See Modifying value lists.
  • Create custom fields to capture additional data. For example, you may want to create a date/time field to capture a due date for items. See Configuring custom fields. You can also create custom fields that automatically calculate read-only values based on other field input values. See Configuring calculated custom fields.
  • Configure requirement types to categorize requirements based on their purpose. Users select a requirement type when adding requirements. See Configuring requirement types.